CVE-2026-2053

CRITICALNVD 10.08.3▼
EchelonGraph scoreMEDIUM confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. NVD baseline CVSS 10.0; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 10.0Exploit: NoneExposed: 0

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

The WSO2 API Manager's message flow component, when processing WS-Addressing headers, does not sufficiently validate or restrict user-controlled input within these headers. This omission allows an attacker to manipulate WS-Addressing headers to specify arbitrary destinations for server-initiated requests.

Successful exploitation allows an unauthenticated attacker to control the destination of server-initiated requests originating from the WSO2 API Manager. This direct control can enable unauthorized access to internal network resources or services that would typically be inaccessible from external networks.

CVSS v3
10.0
EG Score
8.3(medium)
EPSS
12.7%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 27, 2026

Advisory Details (1)

Auto-updated Jul 4, 2026
No patch confirmed yet.
generic

Security Advisory WSO2-2026-5072/CVE-2026-2053

https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5072/

Vendor Advisories for CVE-2026-2053(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 38× in last 7d / 64× 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-07-06 23:12 UTCEG score recompute
  2. 2026-07-06 23:12 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 12:12 UTCEG score recompute
  6. 2026-07-06 12:12 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 01:07 UTCEG score recompute
  10. 2026-07-06 01:07 UTCGHSA enrichment
  11. 2026-07-05 14:07 UTCEG score recompute
  12. 2026-07-05 14:07 UTCGHSA enrichment
  13. 2026-07-05 03:06 UTCEG score recompute
  14. 2026-07-05 03:06 UTCGHSA enrichment
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 16:03 UTCEG score recompute
  17. 2026-07-04 16:02 UTCGHSA enrichment
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 05:01 UTCEG score recompute
  20. 2026-07-04 05:01 UTCGHSA enrichment
  21. 2026-07-03 18:01 UTCEG score recompute
  22. 2026-07-03 18:01 UTCGHSA enrichment
  23. 2026-07-03 07:00 UTCEG score recompute
  24. 2026-07-03 07:00 UTCGHSA enrichment
  25. 2026-07-02 19:56 UTCEG score recompute
Show 39 more
  1. 2026-07-02 19:56 UTCGHSA enrichment
  2. 2026-07-02 08:57 UTCEG score recompute
  3. 2026-07-02 08:57 UTCGHSA enrichment
  4. 2026-07-01 21:54 UTCEG score recompute
  5. 2026-07-01 21:54 UTCGHSA enrichment
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 10:52 UTCEG score recompute
  8. 2026-07-01 10:52 UTCGHSA enrichment
  9. 2026-06-30 23:50 UTCEG score recompute
  10. 2026-06-30 23:50 UTCGHSA enrichment
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-30 12:50 UTCEG score recompute
  13. 2026-06-30 12:49 UTCGHSA enrichment
  14. 2026-06-30 01:49 UTCEG score recompute
  15. 2026-06-30 01:49 UTCGHSA enrichment
  16. 2026-06-29 14:49 UTCEG score recompute
  17. 2026-06-29 14:49 UTCGHSA enrichment
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 03:49 UTCEG score recompute
  21. 2026-06-29 03:49 UTCGHSA enrichment
  22. 2026-06-28 16:48 UTCEG score recompute
  23. 2026-06-28 16:48 UTCGHSA enrichment
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
  26. 2026-06-28 05:47 UTCEG score recompute
  27. 2026-06-28 05:47 UTCGHSA enrichment
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-27 19:41 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
  31. 2026-06-27 18:38 UTCEG score recompute
  32. 2026-06-27 18:38 UTCGHSA enrichment
  33. 2026-06-27 07:38 UTCEG score recompute
  34. 2026-06-27 07:38 UTCGHSA enrichment
  35. 2026-06-27 03:08 UTCEPSS rescore
  36. 2026-06-26 20:38 UTCEG score recompute
  37. 2026-06-26 20:38 UTCGHSA enrichment
  38. 2026-06-26 09:38 UTCEG score recompute
  39. 2026-06-26 09:38 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-2053?
CVE-2026-2053 is a critical vulnerability published on June 26, 2026. The WSO2 API Manager's message flow component, when processing WS-Addressing headers, does not sufficiently validate or restrict user-controlled input within these headers. This omission allows an attacker to manipulate WS-Addressing headers to specify arbitrary destinations for server-initiated…
When was CVE-2026-2053 disclosed?
CVE-2026-2053 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2053 actively exploited?
CVE-2026-2053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-2053?
CVE-2026-2053 has a CVSS v3 base score of 10.0 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.3.
How do I remediate CVE-2026-2053?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2053, 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-2053

Explore →

Is Your Infrastructure Affected by CVE-2026-2053?

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

Start Free Scan →Browse All CVEs