CVE-2026-53780

✕ 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 services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
—
EG Risk
—
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Vendor Advisories for CVE-2026-53780(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 2× in last 7d / 5× 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.

  1. 2026-09-28 09:47 UTCGHSA enrichment
  2. 2026-09-23 05:45 UTCGHSA enrichment
  3. 2026-09-18 05:18 UTCGHSA enrichment
  4. 2026-09-12 02:53 UTCGHSA enrichment
  5. 2026-09-05 21:41 UTCGHSA enrichment
  6. 2026-08-30 06:23 UTCGHSA enrichment
  7. 2026-08-26 12:53 UTCGHSA enrichment
  8. 2026-08-23 13:58 UTCGHSA enrichment
  9. 2026-08-20 18:35 UTCGHSA enrichment
  10. 2026-08-17 23:13 UTCGHSA enrichment
  11. 2026-08-15 03:50 UTCGHSA enrichment
  12. 2026-08-12 08:27 UTCGHSA enrichment
  13. 2026-08-09 13:04 UTCGHSA enrichment
  14. 2026-08-06 17:42 UTCGHSA enrichment
  15. 2026-08-03 22:19 UTCGHSA enrichment
  16. 2026-08-01 02:57 UTCEG score recompute
  17. 2026-08-01 02:57 UTCGHSA enrichment
  18. 2026-07-29 07:32 UTCGHSA enrichment
  19. 2026-07-26 12:09 UTCEG score recompute
  20. 2026-07-26 12:09 UTCGHSA enrichment
  21. 2026-07-23 03:19 UTCEG score recompute
  22. 2026-07-16 09:58 UTCGHSA enrichment
  23. 2026-07-13 14:35 UTCGHSA enrichment
  24. 2026-07-10 19:12 UTCEG score recompute
  25. 2026-07-10 19:12 UTCGHSA enrichment

Frequently asked(3)

What is CVE-2026-53780?
CVE-2026-53780 is a publicly disclosed vulnerability published on July 10, 2026. 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.
When was CVE-2026-53780 disclosed?
CVE-2026-53780 was first published on July 10, 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-53780?
No fix for CVE-2026-53780 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-53780 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53780

Explore →

Is Your Infrastructure Affected by CVE-2026-53780?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs