CVE-2025-4645 json
An ACAP configuration file lacked sufficient input validation, which could allow for arbitrary code execution.
published 11mo ago modified 22d ago also EUVD-2025-74046
- cvss
- 6.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Axis Communications AB AXIS OS 12.6.7
Is CVE-2025-4645 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 11mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.7 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Axis Communications AB AXIS OS
Classification
- Weakness
-
- CWE-1287 Improper Validation of Specified Type of Input
References
-
axis.com
/dam/public/69/47/ff/cve-2025-4645pdf-en-US-504211.pdf
vendor-advisory
Sources
- CVE List CVE-2025-4645
- NVD CVE-2025-4645
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.