dbcve.org
Axis OsOperating system · Axis

CVE-2026-0804

HIGH · 7.3 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 12.10.4 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 a path traversal attack leading to potential 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

This vulnerability involves insufficient input validation in an ACAP configuration file on Axis devices, allowing path traversal attacks. An attacker can exploit this by crafting a malicious ACAP application that manipulates file paths during installation to achieve privilege escalation. The attack requires the victim to install the malicious unsigned ACAP application.

MitigationDisable the ability to install unsigned ACAP applications in the Axis device configuration, and only install ACAP applications from trusted and verified sources. Implement application signature verification before installation.

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.10.4

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. Check the installed Axis OS version
    Access the device web interface and navigate to System > Overview, or use the command line: `cat /etc/axis-release` or `gpcli system info`
    Affected if The installed version is >= 12.0.0 and < 12.10.4, placing it within the affected range
  2. Verify whether unsigned ACAP installation is enabled
    Access the device web interface and navigate to Settings > Apps > Install app, or check via command line: `acap_app_manage --list` and review the device's ACAP signature verification settings in the configuration
    Affected if Unsigned ACAP applications can be installed on the device (the attack requires this condition)
  3. Review installed ACAP applications for suspicious packages
    Navigate to the device's Apps section in the web interface or run `acap_app_manage --list` to enumerate all installed ACAP applications
    Affected if Any unknown, untrusted, or recently installed ACAP applications from unverified sources are present
  4. Inspect for unauthorized file system modifications
    Review critical system directories such as /etc, /var, and /axis for any unexpected files or modifications that may have been created via path traversal during ACAP installation
    Affected if Unexpected files or directories exist in system paths that were not installed by legitimate ACAP applications

The device is affected if it runs Axis OS version 12.0.0 through 12.10.3 and allows installation of unsigned ACAP applications, which is the required condition for exploitation.

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.10.4 or later
Fixed in 12.10.4
Interim mitigation

Disable the ability to install unsigned ACAP applications in the Axis device configuration, and only install ACAP applications from trusted and verified sources. Implement application signature verification before installation.

Recommended fix High confidence

Axis OS 12.10.4 or later

  1. 1. Access the Axis device web interface or use Axis Device Manager to check the current OS version
  2. 2. Navigate to the firmware/update section of the device management interface
  3. 3. Download the Axis OS version 12.10.4 or later from the official Axis website (www.axis.com)
  4. 4. Upload the firmware file to the device and initiate the upgrade process
  5. 5. Wait for the device to reboot and complete the installation
  6. 6. Verify the device is running version 12.10.4 or higher by checking the system information page
  7. 7. After upgrade, ensure the device is configured to disallow unsigned ACAP applications if not already done (Settings > Apps > Allow unsigned apps should be disabled)

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

Fix this in Axis Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0804 — 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-0804 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