CVE-2026-6584NewsPublished 6 Nov 2026

NIST Now Scores Only A Fraction Of New CVEs, And Your Risk Tools May Not Know

Source Reddit ThreatIntel

Compare

Authoritative record:CVE-2026-6584· Medium 5.3

Public exploit available · CVSS 5.3 Medium.

Data as of 13 Nov 2026, 01:39 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
TransformerOptimusSuperAGI	Affected 0.0.1 – 0.0.14 14 affected builds	Fixed in–
PyPIsuperagi`pkg:pypi/superagi`Other threats	Affected 0.0.1 – 0.0.14 14 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Discussion

Since April 2026, NIST has changed its National Vulnerability Database (NVD) scoring policy to assign severity scores only to vulnerabilities under active exploitation or those affecting software critical to the US government. Other CVEs appear in the NVD without NIST severity scores and are marked as Deferred or Not Scheduled. This change causes risk management tools relying solely on NIST scores to deprioritize many vulnerabilities, potentially missing significant threats such as CVE-2026-6584, an authorization bypass with a public exploit but no NIST score. The lack of NIST scoring and default hiding of deferred records in NVD search creates a risk of overlooked vulnerabilities in security workflows.

r/threatintel (opens in a new tab)u/ProfessionalLow88140 points0 comments

Since April 2026, NIST has scored only CVEs under active exploitation and those affecting software the US government depends on. Every other record arrives in the NVD with no NIST score, and the API marks many of them Deferred.

The NVD website now labels the same records "Not Scheduled", so an integration built around the website label will miss every one of them. A missing score is the larger risk. Scanners that rank by NVD severity push these records to the bottom of the queue, including CVE-2026-6584, an authorization bypass in the SuperAGI agent framework with a public exploit.

My NVD developer guide covers how to read vulnStatus and where to source a severity score when NIST hasn't assigned one.

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

Links cited in the discussion

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

Impact

The change in NIST's scoring policy reduces visibility and prioritization of many vulnerabilities in security tools that depend solely on NIST severity scores. This can lead to underestimation of risk and delayed remediation for vulnerabilities that are not actively exploited or not critical to US government software but may still pose significant threats. The default hiding of Deferred/Not Scheduled CVEs in NVD search further exacerbates this risk by preventing some vulnerabilities from reaching security teams. An example is CVE-2026-6584, which has a public exploit but no NIST score, causing it to be deprioritized despite its potential impact.

Defensive guidance

Security teams should not rely exclusively on NIST severity scores for vulnerability prioritization. They should interpret the vulnStatus field in NVD records to identify Deferred or Not Scheduled CVEs and seek severity ratings from alternative sources such as VulDB or CISA KEV data. Tools and workflows should be updated to include these additional data points to avoid missing significant vulnerabilities. The NVD developer guide provides instructions on how to handle records without NIST scores. There is no indication that NIST or the NVD service requires direct action beyond adapting to the new scoring approach.

Summary

The National Vulnerability Database (NVD), maintained by NIST, historically scored every published vulnerability to aid security teams in prioritizing remediation. Due to a 263% increase in CVE submissions from 2020 to 2025, NIST revised its approach in April 2026 to score only vulnerabilities actively exploited or impacting US government software. Other CVEs remain listed but without NIST severity scores, marked as Deferred in the API and Not Scheduled on the website. This results in many vulnerabilities being deprioritized or hidden by tools that rely exclusively on NIST scoring, despite some having significant risk indicated by third-party sources. For example, CVE-2026-6584, an authorization bypass in the SuperAGI framework with public exploit code, lacks a NIST score and is ranked low by NIST-based tools, although VulDB assigns it a CVSS 3.1 score of 5.4. The NVD now requires users to interpret vulnStatus fields and seek alternative severity sources when NIST scores are unavailable.

References

Community reviews

Loading reviews…