dbcve.org
Axis OsOperating system · Axis

CVE-2025-5454

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 12.6.18 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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

A path traversal vulnerability exists in Axis device ACAP configuration files due to insufficient input validation. Successful exploitation requires the device to permit unsigned ACAP applications and victim interaction to install a malicious application, potentially leading to privilege escalation.

MitigationDisable unsigned ACAP application installation on affected Axis devices and only install signed applications from trusted sources. Review and validate ACAP application packages 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.6.18

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/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 Axis OS version
    Access the device web interface and navigate to System > About or use the command 'show version' via SSH/CLI to retrieve the installed Axis OS version number
    Affected if The installed version is >= 12.0.0 and < 12.6.18
  2. Verify unsigned ACAP application permission setting
    Access the device web interface and navigate to Apps > Settings, or check via CLI command 'acap app list' and review the application installation policy settings. Look for a setting controlling unsigned application installation
    Affected if Unsigned ACAP applications are permitted/enabled on the device
  3. Confirm application installation capability
    Verify that the device allows installation of third-party ACAP applications. Check the Apps page in the web interface or use 'acap status' command to see installed applications
    Affected if The device has ACAP application installation capability enabled and applications can be installed

The environment is affected if the Axis OS version falls within 12.0.0 to 12.6.18 AND unsigned ACAP application installation is enabled, allowing a malicious application to be installed for privilege escalation via path traversal.

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.6.18 or later
Fixed in 12.6.18
Interim mitigation

Disable unsigned ACAP application installation on affected Axis devices and only install signed applications from trusted sources. Review and validate ACAP application packages before installation.

Recommended fix High confidence

Axis OS 12.6.18 or later

  1. 1. Identify the current Axis OS version running on the device using the device management interface or Axis Device Manager.
  2. 2. Navigate to the device's web interface and access Settings > System > Maintenance or the equivalent upgrade section.
  3. 3. Upgrade the Axis OS to version 12.6.18 or later (the first fixed release).
  4. 4. After upgrading, navigate to the ACAP settings area in the device configuration.
  5. 5. Verify that the setting for allowing unsigned ACAP applications is disabled or set to 'reject unsigned' to prevent exploitation of this vulnerability.
  6. 6. Alternatively, use Axis Device Manager or ACC (Axis Camera Companion) to push the firmware upgrade to multiple devices if managing a deployment.
Caveat Standard firmware upgrade; review release notes for any changes to ACAP application behavior in 12.6.x releases

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

Fix this in Axis Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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