Code execution via insufficient ACAP validation
Published Nov 11, 2025 · Updated Nov 11, 2025
Improper input validation in AXIS OS 12.0.0 through 12.6.6 allows attackers to execute arbitrary code through a malicious ACAP application. An ACAP configuration file accepts insufficiently validated values, but Axis has not disclosed the specific field or unsafe operation that converts them into code execution. Exploitation requires unsigned ACAP installation to be enabled and a victim to install the malicious application, bounding exposure to devices with that setting enabled.
Summary
What happened
Improper input validation in AXIS OS 12.0.0 through 12.6.6 allows attackers to execute arbitrary code through a malicious ACAP application. An ACAP configuration file accepts insufficiently validated values, but Axis has not disclosed the specific field or unsafe operation that converts them into code execution. Exploitation requires unsigned ACAP installation to be enabled and a victim to install the malicious application, bounding exposure to devices with that setting enabled.
The record
- CVE
- CVE-2025-4645
- Published
- Nov 11, 2025
- Updated
- Nov 11, 2025
- Vendor
- Axis Communications AB
- Product
- AXIS OS
- Classifications
- CWE-1287, T1204.002
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 11, 2025CVE publishedPublication date reported by the CVE source.
- Nov 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.0.0. <12.6.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo