CVE-2026-89212

HIGHPre-NVD 8.68.6
EchelonGraph scoreHIGH confidence

Score 8.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-11. a secondary CVSS source baseline 8.6; sources differ by 0.0.

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

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

A flaw resulting in XML external entity (XXE) was found in Akana API Platform in which references were improperly restricted during XML-to-JSON processing. The issue affects Akana versions 2026.1, 2025.1.1, and all versions before 2024.1.6 (including older unsupported versions of Akana) and has been fixed as a security patch in the latest release of supported versions.

CVSS v3
8.6
EG Score
8.6(high)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

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. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 11, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-89212(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 26× in last 7d / 40× 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-20 20:16 UTCEPSS rescore
  2. 2026-09-20 17:49 UTCGHSA enrichment
  3. 2026-09-20 06:15 UTCGHSA enrichment
  4. 2026-09-19 18:41 UTCEG score recompute
  5. 2026-09-19 18:41 UTCGHSA enrichment
  6. 2026-09-19 07:08 UTCGHSA enrichment
  7. 2026-09-18 19:33 UTCEG score recompute
  8. 2026-09-18 19:33 UTCGHSA enrichment
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 08:21 UTCGHSA enrichment
  11. 2026-09-17 20:47 UTCEG score recompute
  12. 2026-09-17 20:47 UTCGHSA enrichment
  13. 2026-09-17 19:32 UTCEPSS rescore
  14. 2026-09-17 09:14 UTCGHSA enrichment
  15. 2026-09-16 21:41 UTCEG score recompute
  16. 2026-09-16 21:41 UTCGHSA enrichment
  17. 2026-09-16 14:09 UTCEPSS rescore
  18. 2026-09-16 10:08 UTCEG score recompute
  19. 2026-09-16 10:08 UTCGHSA enrichment
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 22:34 UTCGHSA enrichment
  22. 2026-09-15 11:01 UTCEG score recompute
  23. 2026-09-15 11:01 UTCGHSA enrichment
  24. 2026-09-15 03:12 UTCEPSS rescore
  25. 2026-09-14 23:28 UTCGHSA enrichment
Show 15 more
  1. 2026-09-14 11:43 UTCGHSA enrichment
  2. 2026-09-14 00:10 UTCEG score recompute
  3. 2026-09-14 00:10 UTCGHSA enrichment
  4. 2026-09-13 16:48 UTCEPSS rescore
  5. 2026-09-13 12:36 UTCGHSA enrichment
  6. 2026-09-13 01:02 UTCEG score recompute
  7. 2026-09-13 01:02 UTCGHSA enrichment
  8. 2026-09-12 15:02 UTCEPSS rescore
  9. 2026-09-12 13:29 UTCGHSA enrichment
  10. 2026-09-12 01:56 UTCEG score recompute
  11. 2026-09-12 01:56 UTCGHSA enrichment
  12. 2026-09-11 14:23 UTCEG score recompute
  13. 2026-09-11 14:00 UTCEG score recompute
  14. 2026-09-11 13:25 UTCEG score recompute
  15. 2026-09-11 13:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-89212?
CVE-2026-89212 is a high vulnerability published on September 11, 2026. A flaw resulting in XML external entity (XXE) was found in Akana API Platform in which references were improperly restricted during XML-to-JSON processing. The issue affects Akana versions 2026.1, 2025.1.1, and all versions before 2024.1.6 (including older unsupported versions of Akana) and has…
When was CVE-2026-89212 disclosed?
CVE-2026-89212 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89212 actively exploited?
CVE-2026-89212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.9% of all scored CVEs.
What is the CVSS score of CVE-2026-89212?
CVE-2026-89212 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-89212?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-89212, 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-89212

Explore →

Is Your Infrastructure Affected by CVE-2026-89212?

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