CVE-2025-5452
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 · uneditedA malicious ACAP application can gain access to admin-level service account credentials used by legitimate ACAP applications, leading to potential privilege escalation of the malicious ACAP application. 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 confidenceA malicious ACAP application on Axis devices can access admin-level service account credentials used by legitimate ACAP applications, enabling privilege escalation. The attack requires the device to permit unsigned ACAP installations and victim interaction to install the malicious application.
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>= 12.0.0, < 12.6.69CVSS 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
- Network
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check Axis OS versionAccess the device web interface under Settings > System > About, or use the command 'arc --version' via SSH to retrieve the installed firmware versionAffected if Version is 12.0.0 or higher but lower than 12.6.69
-
Verify unsigned ACAP installation policyNavigate to Settings > Apps > Install app in the device web interface and check if the device allows installation of unsigned ACAP applicationsAffected if Unsigned ACAP installations are permitted on the device
-
Review installed ACAP applicationsCheck the list of installed ACAP applications in Settings > Apps, noting any applications from untrusted or unknown sourcesAffected if Any ACAP application has been installed, particularly from untrusted sources
The device is affected if it runs Axis OS version 12.0.0 through 12.6.68 and has unsigned ACAP installation enabled, or if a malicious ACAP application has been installed on the device.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.6.69
Disable the ability to install unsigned ACAP applications in device settings and avoid installing ACAP applications from untrusted sources.
Axis OS 12.6.69 or later
- 1. Access the Axis device web interface or use the Axis IP Utility to check the current Axis OS version.
- 2. Navigate to Settings > System > Upgrade in the web interface.
- 3. Download the latest Axis OS version 12.6.69 or later from the official Axis download portal (www.axis.com).
- 4. Upload and install the new firmware version following the on-screen prompts.
- 5. After upgrade, verify the device is functioning normally and review ACAP application settings.
- 6. As a configuration mitigation: go to Settings > Apps > Settings and ensure the option to allow unsigned ACAP applications is disabled (uncheck 'Allow unsigned apps').
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5452 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5452 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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