dbcve.org
Axis OsOperating system · Axis

CVE-2025-4645

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 12.6.7 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 for arbitrary code execution. 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 exists in ACAP (AXIS Camera Application Platform) configuration file handling where insufficient input validation allows arbitrary code execution when a malicious ACAP application is installed. The attacker requires the victim to install a crafted application on a device already configured to permit unsigned ACAP applications.

MitigationDisable unsigned ACAP application installation in the Axis device management interface and only install ACAP applications from trusted, verified sources. Review existing device configurations to ensure unsigned app installation is restricted.

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

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 > Overview, or use the command 'curl -u admin:pass http://<device-ip>/axis-cgi/admin/param.cgi?action=list&group=Properties.Firmware' to retrieve the firmware version
    Affected if The installed version is 12.0.0 or higher but lower than 12.6.7
  2. Verify unsigned ACAP application setting
    Access the device web interface and go to Apps > Settings, or use the command 'curl -u admin:pass http://<device-ip>/axis-cgi/param.cgi?action=list&group=appmgr' to check the app manager configuration
    Affected if Unsigned ACAP application installation is permitted on the device
  3. Review installed ACAP applications
    Access the device web interface under Apps > My Apps, or use thecommand 'curl -u admin:pass http://<device-ip>/axis-cgi/param.cgi?action=list&group=appmgr' to list all installed applications
    Affected if Any ACAP application is installed from an untrusted or unverified source
  4. Inspect ACAP configuration files
    Use the command 'ls -la /usr/local/acap/' or access the device configuration to examine ACAP application configuration directories for unexpected or tampered configuration files
    Affected if Unexpected configuration files exist in ACAP directories or configuration files contain suspicious content

The device is affected if it runs Axis OS version 12.0.0 through 12.6.6 and has unsigned ACAP application installation enabled, regardless of whether malicious apps are currently installed.

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

Disable unsigned ACAP application installation in the Axis device management interface and only install ACAP applications from trusted, verified sources. Review existing device configurations to ensure unsigned app installation is restricted.

Recommended fix Moderate confidence

Axis OS 12.6.7 or later

  1. 1. Identify the Axis device(s) on your network that are running Axis OS version 12.0.0 or higher.
  2. 2. Access the device's web interface or use Axis Device Manager to check the current Axis OS version.
  3. 3. Confirm the current version is >= 12.0.0 and < 12.6.7 to determine if the device is affected.
  4. 4. Backup the device configuration before performing the upgrade.
  5. 5. Download Axis OS version 12.6.7 or later from the official Axis website.
  6. 6. Upload and install the new Axis OS firmware through the device's web interface or management tool.
  7. 7. After upgrade, verify the device is running version 12.6.7 or later.
  8. 8. Review device settings to ensure unsigned ACAP application installation is disabled unless explicitly required, to reduce attack surface.
Caveat As with any firmware upgrade, review ACAP application compatibility with the new OS version before deploying to production devices

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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