- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2025 02:56 AM
Hello.
I saw NVD got maintenance windows somewhere about 24th July 2025.
Now the integrations stopped to work.
Error: Invalid response code received from NVD: Not Found 404 The URL is incorrect
Any one contacted NVD or fixed this issue ?
We tried to use many different API Keys - still the same issue.
BR
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2025 12:34 AM
We do have an open PRB for this: PRB1921244.
We'll make this fix and release it soon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2025 04:04 PM
Guyz, I can see following, so should be good to upgrade and get the fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2025 04:45 AM
I am also experiencing this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2025 05:03 AM
Our version of "Vulnerability Response Integration with NVD" is 1.5.3, and I see that 1.6.1 is available (I have an upgrade request pending internally). What version are you running?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2025 06:38 AM
A recent update to the NVD API is causing the "NIST National Vulnerability Database Integration - API (CVE only)" and "NIST National Vulnerability Database Integration - API (CPE only)" to fail with a 404 error. This issue affects only this specific integration. Other NVD integrations, such as "NIST National Vulnerability Database Integration - API (Unmapped CPE)", continue to function as expected.
To resolve this issue, please follow the steps mentioned in the KB2332829
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2025 07:29 AM
This change did work for me, thanks! Is this fix included in version 1.6.1 of the NVD integration store app? Or will it be included in a later release?