Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-2710 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE-2026-2710
✕ Withdrawn — historical dataUNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: —CVSS v2: —Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- EG Score
- 0.0(none)
- EG Risk
- 0EG Risk 0/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses intrinsic severity with real-world exploitation and automatability, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. It is distinct from the 0–10 EG Score, which measures severity.
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
May 7, 2026
Last Modified
May 7, 2026
Vendor Advisories for CVE-2026-2710(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Data Freshness Timeline
(refreshed 1× in last 7d / 1× in last 30d)
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.
- 2026-07-23 03:07 UTCEG score recompute
- 2026-06-26 22:05 UTCGHSA enrichment
- 2026-06-17 02:35 UTCGHSA enrichment
- 2026-06-14 03:29 UTCGHSA enrichment
- 2026-06-10 04:53 UTCGHSA enrichment
- 2026-06-07 06:14 UTCGHSA enrichment
- 2026-06-04 07:34 UTCGHSA enrichment
- 2026-06-01 08:53 UTCGHSA enrichment
- 2026-05-20 13:50 UTCEG score recompute
- 2026-05-20 13:50 UTCGHSA enrichment
Frequently asked(3)
What is CVE-2026-2710?
CVE-2026-2710 is a publicly disclosed vulnerability published on May 7, 2026. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
When was CVE-2026-2710 disclosed?
CVE-2026-2710 was first published in the National Vulnerability Database on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
How do I remediate CVE-2026-2710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2710, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-2710
Is Your Infrastructure Affected by CVE-2026-2710?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.