Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority...
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
MITRE marked CVE-2025-25275 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority...
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused
August 12, 2026
August 12, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Explore the affected products and dependency analysis for CVE-2025-25275
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.