dbcve.org
Axis OsOperating system · Axis

CVE-2025-8108

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 12.7.33 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 has improper permissions and lacks input validation, which could 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

The vulnerability stems from improper file permissions on ACAP configuration files combined with missing input validation, which could allow a malicious ACAP application to escalate privileges. Successful exploitation requires the device to allow unsigned ACAP installations and user interaction to install the malicious application.

MitigationDisable unsigned ACAP application installation in device settings if possible, and only install ACAP applications from trusted sources. Monitor for any unexpected ACAP installations.

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.7.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
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
    Log into the device web interface and navigate to System > About, or query the device API at /axis-cgi/sysinfo.cgi to find the firmware version
    Affected if The installed version is >= 12.0.0 and < 12.7.33
  2. Verify unsigned ACAP installation setting
    In the device web interface, go to Apps settings and check whether unsigned or untrusted ACAP applications are permitted to be installed
    Affected if Unsigned ACAP installation is enabled on the device
  3. Review installed ACAP applications
    Navigate to the Apps section of the device web interface or query the device API to list all installed ACAP applications
    Affected if Any unexpected or untrusted ACAP applications are present on the device

The device is affected if it runs Axis OS version 12.0.0 through 12.7.32, allows unsigned ACAP installations, and has a malicious ACAP application 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.7.33 or later
Fixed in 12.7.33
Interim mitigation

Disable unsigned ACAP application installation in device settings if possible, and only install ACAP applications from trusted sources. Monitor for any unexpected ACAP installations.

Recommended fix High confidence

Axis OS version 12.7.33 or later

  1. 1. Log into the Axis device web interface using administrator credentials
  2. 2. Navigate to System > Firmware to check the current Axis OS version
  3. 3. Download the latest Axis OS firmware version 12.7.33 or later from the official Axis website (www.axis.com)
  4. 4. In the device web interface, select the downloaded firmware file and click Install
  5. 5. Wait for the firmware installation to complete and the device to reboot
  6. 6. After reboot, verify the new firmware version is installed under System > Firmware
  7. 7. As an additional security measure, navigate to the ACAP settings and ensure 'Allow unsigned ACAP applications' is disabled unless explicitly required for legitimate applications
Caveat Review Axis release notes for version 12.7.x to check for any breaking changes specific to your device model and deployed ACAP applications

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-2025-8108 — 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-8108 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