CVE-2026-89212
8.6Perforce · Akana API Platform
A critical XML external entity (XXE) vulnerability in the Akana API Platform allows unauthenticated attackers to perform unauthorized data extraction via improper XML-to-JSON processing.
Executive summary
A critical XML external entity (XXE) vulnerability in the Perforce Akana API Platform allows unauthenticated remote attackers to bypass security controls and access sensitive system data.
Vulnerability
This vulnerability is an improper restriction of XML external entity references (CWE-611) occurring during the XML-to-JSON conversion process. The flaw is remotely exploitable without authentication, allowing attackers to force the application to process malicious XML input.
Business impact
Successful exploitation of this XXE vulnerability can lead to the exposure of sensitive files on the host server, internal network scanning, or local service disruption. Given the CVSS score of 8.6, this represents a high-severity risk to confidentiality, potentially exposing proprietary business data or credentials stored within the application environment.
Remediation
Immediate Action: Upgrade to the fixed versions provided by the vendor: 2024.1.6, 2025.1.2, or 2026.2.
Proactive Monitoring: Monitor application access logs for unusual XML payloads or requests targeting internal file paths, such as those referencing etc/passwd or internal network configuration files.
Compensating Controls: Deploy a Web Application Firewall (WAF) configured to inspect incoming XML traffic and block requests containing DTD or external entity declarations.
Exploitation status
Public Exploit Available: No
Analyst recommendation
The severity of this vulnerability necessitates immediate action. Administrators must prioritize patching the Akana API Platform to the specified secure versions to eliminate the risk of unauthenticated remote data extraction. If an immediate upgrade is not feasible, ensure that network-level controls are in place to restrict access to the affected API endpoints.
More Perforce CVEs
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section
Sources
Originally found and disclosed by Yoeri Vegt, per the CVE Program record.