Skip to main content
VulnerabilityPublished Updated

CVE-2025-30025: AXIS Device Manager · Deserialization of Untrusted Data

Affects AXIS Device ManagerSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium : upgrade to 5.32 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.32
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade AXIS Device Manager to 5.32.

Affected software

ProductAffectedFixed in
Axis Communications AB AXIS Device ManagerAffected
  • <5.32
Fixed in
  • 5.32

AI-suggested

To mitigate CVE-2025-30025, organizations should prioritize upgrading AXIS Device Manager to version 5.32 or later once available, as this will contain the necessary fixes to address the deserialization flaw. If you cannot patch yet, restrict local access to the management servers strictly to trusted and authenticated personnel. Implement strict access controls and monitoring on systems running AXIS Device Manager to detect any unauthorized local activity. Employ application whitelisting and endpoint protection solutions to prevent execution of unauthorized code. Network segmentation should be used to isolate management servers from general user networks, reducing the risk of lateral movement. Regularly audit and review user privileges on these systems to minimize the number of users with local access. Consider implementing host-based intrusion detection systems to alert on suspicious process or protocol activities related to the device manager.

Description

The communication protocol used between the server process and the service control had a flaw that could lead to a local privilege escalation.

References

Community reviews

Loading reviews…