CVE-2026-85978: Unauthenticated Remote Code Execution in Akana API Platform
An unauthenticated remote code execution vulnerability exists in the Policy Manager console of Akana API Platform. A path normalization discrepancy between the authentication filter and the servlet dispatcher allows a crafted request to bypass authentication and reach an endpoint that evaluates attacker-supplied script code without sandboxing, resulting in arbitrary code execution. Exploitation requires no authentication or user interaction.
Security readout for executives and security teams
Plain-English summary
Akana API Platform’s Policy Manager console can reportedly be taken over remotely without credentials or user action. A successful attacker could run arbitrary code, potentially compromising the platform and connected systems. The CVSS 4.0 score is 10.0, making exposed deployments an immediate remediation priority.
Executive priority
Treat this as an immediate priority for any reachable Policy Manager deployment. Identify exposed instances, restrict access, and engage Perforce for definitive remediation guidance. Because compromise could affect confidentiality, integrity, and availability across connected systems, potentially affected internal instances should also receive urgent review.
Technical view
A path-normalization mismatch between the authentication filter and servlet dispatcher permits authentication bypass. A crafted request can reach an endpoint that evaluates attacker-controlled script code without sandboxing, producing unauthenticated remote code execution. The record maps this to CWE-41, CWE-863, and CWE-94.
Likely exposure
Deployments using the listed Akana versions are potentially affected, particularly when the Policy Manager console is reachable from untrusted networks. The supplied version list includes releases before 2024.1 and specified 2024.1, 2025.1, and 2026 releases, but its formatting is ambiguous and should be confirmed with Perforce.
Exploitation context
Exploitation reportedly requires network access only, with low complexity, no privileges, and no user interaction. The supplied sources do not establish active exploitation, public exploit availability, or CISA KEV listing. Absence from KEV should not be treated as evidence that exploitation has not occurred.
Researcher notes
The supplied record describes an authentication-filter versus servlet-dispatcher normalization discrepancy leading to unsandboxed script evaluation. The affected-version field is unusually formatted and may conflate version ranges or remediation information. Validate version applicability against the live Perforce advisory before making closure decisions. No active exploitation evidence is supplied.
Mitigation direction
Review the Perforce advisory and obtain confirmed fixed-version guidance.
Restrict Policy Manager console access to trusted administrative networks.
Remove public exposure using firewall, proxy, or access-control rules.
Prioritize upgrades or vendor-provided remediation once applicability is confirmed.
Increase monitoring for anomalous Policy Manager requests and unexpected process activity.
Validation and detection
Inventory Akana API Platform and Policy Manager versions across all environments.
Verify whether each Policy Manager console is reachable from untrusted networks.
Compare installed versions directly against Perforce’s current advisory.
Review access, application, and host logs for suspicious unauthenticated requests.
Confirm restrictions and remediation using non-destructive authenticated administrative checks.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-41: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-41 · source CWE mapping
Improper Resolution of Path Equivalence
Improper Resolution of Path Equivalence represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.