EUVD-2026-55966
GHSA-h4gf-wr33-6635
Severity by source
AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:L
Local vector and PR:H reflect admin-controlled installation prerequisite; AC:H captures the race condition timing requirement; C:H reflects credential and video feed exposure post-escalation.
Primary rating from Vendor (Axis).
CVSS VectorVendor: Axis
Lifecycle Timeline
2DescriptionCVE.org
The ACAP framework contains a Time-of-Check to Time-of-Use (TOCTOU) race condition, which could potentially lead to privilege escalation. This vulnerability can only be exploited if the Axis device is configured to allow the installation of unsigned ACAP applications, and if an attacker convinces the victim to install a malicious ACAP application.
AnalysisAI
Privilege escalation in the Axis Camera Application Platform (ACAP) framework on Axis OS exploits a Time-of-Check to Time-of-Use (TOCTOU) race condition during ACAP application installation. Exploitation is gated behind two explicit non-default conditions: the target device must have unsigned ACAP application installation enabled, and a high-privileged victim must be socially engineered into installing a malicious package. No public exploit code has been identified at time of analysis, and the vendor-assigned CVSS score of 5.1 (Medium) accurately reflects the high attack complexity and privilege prerequisites that substantially constrain real-world impact.
Technical ContextAI
ACAP (Axis Camera Application Platform) is Axis Communications' proprietary runtime for deploying third-party applications on Axis network cameras, encoders, and video surveillance appliances running Axis OS. The root cause is CWE-367 (Time-of-Check to Time-of-Use), a class of race condition where a security-relevant check - in this case, verification of an application's signature or integrity - occurs at one moment in time, but the actual resource use (execution or installation of that application) occurs at a later moment. An attacker can substitute a malicious payload between these two events, bypassing the integrity check. The affected CPE, cpe:2.3:a:axis_communications_ab:axis_os:*:*:*:*:*:*:*:*, covers all versions of Axis OS without specifying a fixed upper bound, indicating broad version exposure pending vendor clarification. The vulnerability was disclosed directly by Axis Communications.
RemediationAI
Consult the Axis vendor advisory at https://www.axis.com/dam/public/fd/16/ab/cve-2026-6505pdf-en-US-543641.pdf for patched Axis OS firmware versions; the exact fix version was not confirmed from the data available at time of analysis, so the advisory is the authoritative source. The single most effective immediate compensating control is to disable the option to allow installation of unsigned ACAP applications on all Axis devices - this eliminates the attack surface entirely, since the vulnerability cannot be triggered without this non-default setting enabled. The trade-off is that any legitimate unsigned ACAP applications already deployed will cease to install or update until re-signed. Additionally, restrict administrative access to device management interfaces to the minimum set of trusted personnel using role-based access controls and MFA where supported, reducing the social engineering surface required by the UI:R prerequisite. Device management should be confined to a dedicated out-of-band VLAN to reduce lateral access opportunities.
Privilege escalation in Axis VAPIX framework.
Privilege escalation vulnerability in Axis Communications' VAPIX Device Configuration framework that allows a local, aut
A user controlled parameter related to SMTP test functionality is not correctly validated making it possible to add the
During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the ACAP Appli
Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API overlay_del.cgi is vulnerable to pa
During an annual penetration test conducted on behalf of Axis Communication, Truesec discovered a flaw in the VAPIX Devi
A user controlled parameter related to SMTP test functionality is not correctly validated making it possible to bypass b
Remote code execution via improper input validation in a VAPIX API parameter on Axis OS affects Axis network camera and
GoSecure on behalf of Genetec Inc. Rated high severity (CVSS 7.2), this vulnerability is remotely exploitable, low attac
The VAPIX API mediaclip.cgi that did not have a sufficient input validation allowing for a possible remote code executio
Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API irissetup.cgi was vulnerable to pat
Sandro Poppi, member of the AXIS OS Bug Bounty Program, has found that the VAPIX API manageoverlayimage.cgi was vulnerab
Same technique Privilege Escalation
View allShare
External POC / Exploit Code
Leaving vuln.today