# CVE-2026-89212: XML External Entity in Akana API Platform

> Attackers can exploit XML external entity flaws in Akana API Platform to read sensitive data or cause denial of service.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-58hf-8fhw-r5mw

## What is CVE-2026-89212?

CVE-2026-89212 is a critical vulnerability in Perforce Akana, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2026-89212?


## How do I fix CVE-2026-89212?

No fix has been published for CVE-2026-89212 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-89212 being exploited?

There is no known exploitation of CVE-2026-89212 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-89212 and fix it if it is affected.

What it is: CVE-2026-89212 is a critical vulnerability in Perforce Akana, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89212 in the wild and no public exploit code.

Affected product: Perforce Akana. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-89212/ (Markdown: https://insights.sbomify.com/CVE-2026-89212/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-89212
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-89212
- OSV: https://osv.dev/vulnerability/CVE-2026-89212

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-89212/
Summaries are generated and may contain mistakes; the official description above is the record.