CVE-2026-85978 in Akanainfo

Summary

by MITRE • 09/09/2026

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.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 09/09/2026

The vulnerability identified within the Akana API Platform Policy Manager console represents a critical security flaw rooted in architectural inconsistencies between access control mechanisms and request routing logic. Specifically, this is an unauthenticated remote code execution (RCE) vulnerability that stems from a path normalization discrepancy. In web application architectures, it is standard practice to implement authentication filters at the front end of the request processing pipeline to validate user credentials before allowing requests to reach backend servlets or controllers. However, in this instance, there exists a divergence in how the authentication filter and the subsequent servlet dispatcher interpret URL paths. This inconsistency allows an attacker to craft specific HTTP requests that exploit differences in path parsing logic, effectively bypassing the intended authentication gateways. The core technical flaw lies in the failure of the application to consistently normalize or canonicalize input paths across different layers of its processing stack, a classic example of CWE-284 Improper Access Control combined with CWE-79 Cross-site Scripting principles when applied server-side for code evaluation.

The operational impact of this vulnerability is severe due to the nature of the affected endpoint and the lack of required user interaction or authentication. Once an attacker successfully bypasses the authentication filter through path manipulation, they gain access to a specific endpoint designed to evaluate script code. Crucially, this endpoint does not implement adequate sandboxing mechanisms for the executed scripts. Sandbox failures are typically categorized under CWE-697 Incorrect Comparison and CWE-829 Inclusion of Functionality from Untrusted Control Sources when the context involves executing arbitrary logic. Without proper isolation or restriction on the execution environment, any script code submitted by an attacker is interpreted and run with the same privileges as the underlying application process. This means that a remote, unauthenticated adversary can inject malicious payloads to achieve full control over the server hosting the Akana API Platform Policy Manager console.

From a threat intelligence perspective, this vulnerability aligns closely with MITRE ATT&CK techniques related to initial access and execution. The ability to bypass authentication maps directly to T1078 Valid Accounts or more specifically T1528 Steal Application Access Token if tokens were involved, but in this case, it is purely a logic flaw allowing unauthenticated entry (T1190 Exploit Public-Facing Application). Once inside, the execution of arbitrary scripts corresponds to T1059 Command and Scripting Interpreter. The lack of sandboxing exacerbates the risk by enabling lateral movement or persistence if the server environment allows for further exploitation based on initial code execution. This scenario highlights a critical failure in defense-in-depth strategies where input validation and access control are not uniformly applied across all components of the request lifecycle.

Mitigation efforts must prioritize immediate patching to address the path normalization logic within both the authentication filter and the servlet dispatcher, ensuring that canonicalized paths are consistently validated before any processing occurs. In addition to software updates, organizations should implement strict input validation on all script evaluation endpoints, enforcing allow-lists for permitted characters or functions if such functionality is required. Network-level controls such as Web Application Firewalls (WAF) can provide temporary relief by detecting and blocking known exploitation patterns associated with path traversal or unauthorized access attempts. Furthermore, reviewing the application architecture to ensure that security checks are applied uniformly regardless of entry point variations is essential for preventing similar logic flaws in other modules. Regular penetration testing focusing on authentication bypasses and server-side code injection scenarios will help identify residual risks before they can be exploited by malicious actors targeting critical API management infrastructure.

Responsible

Perforce

Reservation

09/04/2026

Disclosure

09/09/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

low

Sources

Do you know our Splunk app?

Download it now for free!