dbcve.org
Axis OsOperating system · Axis

CVE-2025-3892

MEDIUM · 6.7 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 12.5.31 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
ACAP applications can be executed with elevated privileges, potentially leading 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

ACAP applications on Axis devices can be executed with elevated privileges when the device is configured to allow unsigned ACAP applications, potentially enabling privilege escalation if an attacker convinces a victim to install a malicious application.

MitigationDisable the configuration option allowing installation of unsigned ACAP applications in the Axis device settings, and only install signed ACAP applications from trusted sources.

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

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 or use the Axis CLI to retrieve the installed Axis OS version. Compare the version number against the affected range: 12.0.0 to 12.5.31 (versions 12.0.0 through 12.5.30 are affected).
    Affected if The device runs Axis OS version 12.0.0 or higher but lower than 12.5.31.
  2. Verify unsigned ACAP application setting
    Navigate to the device settings in the Axis web interface, typically under System > Security or Applications settings, and locate the configuration option that controls whether unsigned ACAP applications can be installed or executed.
    Affected if The option to allow unsigned ACAP applications is enabled on the device.
  3. Review installed ACAP applications
    Access the device's application management interface to list all installed ACAP applications. Check the application signatures or integrity status if this information is displayed.
    Affected if Any unsigned ACAP applications are installed on the device.
  4. Check for unauthorized or unknown applications
    Review the list of installed ACAP applications and verify that all applications were intentionally installed from trusted sources.
    Affected if Unknown or unexpected ACAP applications are present that were not deliberately installed.

The device is affected if it runs Axis OS version 12.0.0 through 12.5.30 AND has the configuration that permits unsigned ACAP applications enabled.

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.5.31 or later
Fixed in 12.5.31
Interim mitigation

Disable the configuration option allowing installation of unsigned ACAP applications in the Axis device settings, and only install signed ACAP applications from trusted sources.

Recommended fix High confidence

Axis OS 12.5.31 or later

  1. Log in to the Axis device web interface or use Axis Device Manager to check the current OS version
  2. Navigate to the firmware or system upgrade section
  3. Download Axis OS version 12.5.31 or later from the official Axis website (www.axis.com)
  4. Upload and install the firmware upgrade following Axis's standard upgrade procedure
  5. After reboot, verify the device is running version 12.5.31 or later
  6. As a secondary mitigation, ensure the device is NOT configured to allow installation of unsigned ACAP applications unless absolutely necessary

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
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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