dbcve.org
Axis OsOperating system · Axis

CVE-2025-6779

MEDIUM · 6.7 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 12.6.40 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, which could allow command injection and 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 · high confidence

This vulnerability exists in Axis devices running ACAP (Axis Communications Application Platform). An ACAP configuration file has improper file permissions, which can be exploited to achieve command injection and privilege escalation. The attack requires both a specific device configuration (allowing unsigned ACAP applications) and user interaction (convincing the victim to install a malicious ACAP application).

MitigationDisable the installation of unsigned ACAP applications in the Axis device configuration settings, and only install ACAP applications from trusted sources. Apply vendor firmware updates when available.

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

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 command 'axsysinfo' or check /etc/axis-os.conf for the firmware version
    Affected if The installed version is >= 12.0.0 and < 12.6.40
  2. Verify unsigned ACAP application setting
    In the device web interface, navigate to Settings > Apps > Settings (or equivalent) and check if the option to allow unsigned/insecure apps is enabled; alternatively, check via CLI using the ACAP API or configuration files
    Affected if The device configuration allows installation of unsigned ACAP applications
  3. Inspect ACAP configuration file permissions
    Access the device via SSH and examine the file permissions of ACAP configuration files in /etc/acap/ or /var/acap/ using 'ls -la'
    Affected if Configuration files have overly permissive permissions (e.g., world-writable or writable by non-privileged users)
  4. Review installed ACAP applications
    In the device web interface under Apps, list all installed ACAP applications; via CLI, check /var/acap/ or use 'acap list' command
    Affected if There are any ACAP applications installed from untrusted or unknown sources, especially if the device allows unsigned apps

The device is affected if it runs Axis OS version 12.0.0 through 12.6.39 AND has unsigned ACAP application installation enabled in its configuration settings.

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

Disable the installation of unsigned ACAP applications in the Axis device configuration settings, and only install ACAP applications from trusted sources. Apply vendor firmware updates when available.

Recommended fix High confidence

Axis OS 12.6.40 or later

  1. Log into the Axis device web interface or use AXIS Device Manager to check the current OS version
  2. Navigate to System > About or Settings > System > Maintenance to verify the installed OS version
  3. If the version is >= 12.0.0 and < 12.6.40, the device is vulnerable
  4. Upgrade the Axis OS to version 12.6.40 or later via the device web interface (Settings > System > Maintenance > Upgrade) or using AXIS Device Manager
  5. After upgrade, verify the new version is 12.6.40 or higher
  6. As an additional mitigation: Go to Settings > Apps > ACAP settings and ensure 'Allow unsigned ACAP applications' is DISABLED to prevent exploitation
Caveat Verify ACAP application compatibility with the new OS version before production deployment; review Axis release notes for any known issues

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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