dbcve.org
Axis OsOperating system · Axis

CVE-2026-0802

HIGH · 7.3 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 12.9.33 or later.
See remediation →
73/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An ACAP configuration file lacked sufficient input validation, which could allow command injection and 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Axis ACAP applications contain a configuration file with insufficient input validation, allowing command injection when a malicious unsigned ACAP application is installed. An attacker must trick a user into installing a crafted ACAP app while the device allows unsigned applications, potentially achieving privilege escalation.

MitigationDisable the ability to install unsigned ACAP applications in device settings. Only install ACAP applications from trusted, verified sources. Apply any available Axis firmware updates that address this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Axis OsOperating system
Affected:>= 12.0.0, < 12.9.33

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device and confirm it runs Axis OS
    Access the device web interface or use the Axis IP utility to confirm the device model and that it runs Axis OS firmware
    Affected if The device is an Axis camera or device running Axis OS firmware
  2. Check the installed Axis OS version
    Navigate to the device web interface System > About or use the command line to retrieve the firmware version (typically shown on the System info page or via the API)
    Affected if The installed version is >= 12.0.0 and < 12.9.33
  3. Verify if unsigned ACAP application installation is permitted
    Locate the ACAP application settings in the device web interface (typically under Apps or System > Security) and check whether the option to allow unsigned or untrusted ACAP applications is enabled
    Affected if The device is configured to allow installation of unsigned ACAP applications

A user is affected if the Axis OS version falls within 12.0.0 to 12.9.32 and the device is set to permit installation of unsigned ACAP applications, enabling the command injection path.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.9.33 or later
Fixed in 12.9.33
Interim mitigation

Disable the ability to install unsigned ACAP applications in device settings. Only install ACAP applications from trusted, verified sources. Apply any available Axis firmware updates that address this vulnerability.

Recommended fix High confidence

Axis OS version 12.9.33 or later

  1. 1. Access the Axis device web interface or use Axis Device Manager to check the current firmware version.
  2. 2. Navigate to the firmware update section in the device settings.
  3. 3. Download the latest Axis OS firmware version 12.9.33 or later from the official Axis website (www.axis.com/support/firmware).
  4. 4. Upload and install the firmware update to the device.
  5. 5. After the update completes, verify the device is running version 12.9.33 or later.
  6. 6. As an additional security measure, ensure the device is NOT configured to allow installation of unsigned ACAP applications unless absolutely necessary for your use case.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Axis Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0802 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data