CVE-2026-79403 in Kilo Code
Summary
by MITRE • 09/29/2026
An issue in Kilo Code before v7.4.1 allows a local attacker to execute arbitrary code via the permission/allow-everything endpoint
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 09/29/2026
The vulnerability identified in versions of Kilo Code prior to version 7.4.1 represents a critical security flaw within the application's authorization logic, specifically targeting the internal management endpoints used for configuration and access control. This issue centers on the improper implementation of permissions associated with the allow-everything endpoint, which is designed to grant comprehensive administrative privileges or bypass standard restriction mechanisms under specific conditions. In a properly secured system, such high-privilege operations should be strictly gated behind robust authentication checks, multi-factor verification, and explicit user consent to prevent unauthorized escalation. However, in this instance, the mechanism fails to adequately validate whether the initiating request originates from an authorized administrator or if it is being proxied through a less privileged context that inadvertently gains elevated access rights.
From a technical perspective, the flaw stems from insufficient input validation and lack of strict enforcement on the permission scope when interacting with the allow-everything interface. An attacker who has achieved local access to the system can exploit this misconfiguration by crafting specific HTTP requests or API calls directed at this endpoint. Because the application does not sufficiently distinguish between legitimate administrative intent and malicious exploitation, it processes these requests as valid commands for granting unrestricted permissions. This effectively allows a user with even minimal local privileges to escalate their rights to that of an administrator or superuser within the Kilo Code environment. The absence of proper session validation or token verification during this specific operation creates a direct path for privilege escalation without requiring complex exploitation techniques beyond basic network interaction capabilities available on the host machine.
The operational impact of this vulnerability is severe, as it compromises the integrity and confidentiality of the entire system managed by Kilo Code. Once an attacker successfully executes arbitrary code via this endpoint, they gain full control over the application's configuration, potentially allowing them to modify settings, access sensitive data stored within the platform, or install malicious extensions that persist across sessions. This level of access can lead to complete system compromise, where the attacker can pivot to other networked systems if Kilo Code is integrated with broader infrastructure tools such as CI/CD pipelines or remote development environments. The ability to execute arbitrary code means that an adversary could deploy malware, exfiltrate proprietary source code, or disrupt service availability by altering critical operational parameters, thereby undermining trust in the software's reliability and security posture.
This vulnerability aligns closely with CWE-269, which describes Improper Privilege Assignment, as it involves granting excessive permissions to a user who should not possess them based on their initial role. Furthermore, from an offensive security standpoint, this behavior is characteristic of ATT&CK technique T1078, Valid Accounts, where attackers leverage legitimate credentials or access paths to move laterally and escalate privileges within a target environment. The exploitation vector being local also highlights the importance of defense-in-depth strategies, as perimeter defenses alone cannot mitigate risks arising from insider threats or compromised workstations that have physical or logical proximity to the application server.
To mitigate this risk, organizations must immediately upgrade Kilo Code to version 7.4.1 or later, where these permission checks and endpoint validations have been corrected by the developers. Until an update is applied, administrators should restrict network access to the management interfaces of Kilo Code using firewall rules that limit connectivity to trusted IP addresses only. Additionally, implementing strict role-based access control policies ensures that even if such endpoints are accessible, they remain protected behind strong authentication mechanisms requiring multi-factor verification for any administrative action. Regular auditing of user permissions and monitoring logs for unusual activity patterns related to privilege changes can also help detect potential exploitation attempts early, reducing the window of exposure in environments where immediate patching is not feasible due to operational constraints.