Skip to content

About

Cybersecurity tools trust NVD severity scores to rank risk, yet since April 2026 many new CVEs arrive without one. Accurate prioritization now depends on reading NVD vulnerability data beyond the score and identifying high-risk flaws NIST has not assessed.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

39 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

NVD CVE API Developer Guide

The National Vulnerability Database (NVD), maintained by the US National Institute of Standards and Technology (NIST), is the reference most security teams rely on to assess newly disclosed software flaws. Its severity scores, delivered through the NVD CVE API, determine how scanners and patch management tools prioritise remediation.

Live guide: https://archanacontent.github.io/nvd-cve-api-docs/

The Problem

  • What Changed - NIST previously aimed to analyse and score every vulnerability published in the NVD. With submissions up 263% between 2020 and 2025, that model became unsustainable. Since April 2026, NIST has scored only vulnerabilities under active exploitation and those affecting software the US government depends on.
  • What Breaks - Every other CVE still appears in the NVD, but without a severity score from NIST. Many carry a Deferred status in the API, shown as "Not Scheduled" on the NVD website, NIST's signal that no review is planned. Tools that sort flaws by score push these records to the bottom of the list. NVD search also hides deferred records by default, so some never reach the team responsible for fixing them.
  • Real Example - CVE-2026-6584, an authorization bypass in the open-source AI agent framework SuperAGI, was published in April 2026 without a NIST score. Its status reads Deferred in the API and "Not Scheduled" on the website. The only scores come from VulDB, including a CVSS 3.1 rating of 5.4. Tools that read only NIST's score rank it among the lowest priorities, although nothing about the vulnerability indicates low severity.

What's Inside

Guide What you'll learn Status
Quickstart Retrieve one CVE and read the fields that show severity and exploitation Published
Reading Records After The 2026 Change How to judge a record by its vulnStatus and find a score when NIST hasn't assigned one Published
AI Draft Audit: Gemini On The NVD CVE API Fifteen errors in one AI-generated guide, and the method that catches them Published
LLM Evaluation Kit: CVE Severity Answers ChatGPT and Gemini scored against the live NVD record, with a rubric, preference pairs and red-team prompts Published
In-App Guidance The design and JSON definition behind the docs onboarding flow Published
How-To: Find Actively Exploited Vulnerabilities Filtering for CVEs listed in CISA's KEV catalog Planned
Parameter Reference Each query parameter with its type and a working example Planned
Troubleshooting Fixes for rate limits, authentication errors and empty results Planned

Background Reading

API responses captured from the live NVD API, October 2026, and rechecked on November 1, 2026.

License

Licensed under CC BY 4.0.

Author

Written and maintained by Archana Panda, Senior Technical Writer.

About

Cybersecurity tools trust NVD severity scores to rank risk, yet since April 2026 many new CVEs arrive without one. Accurate prioritization now depends on reading NVD vulnerability data beyond the score and identifying high-risk flaws NIST has not assessed.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors