Skip to main content
VulnerabilityPublished Updated

CVE-2025-22937: Improper Privilege Management

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Mar 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

AI-suggested

  1. Immediate Network Segmentation: Isolate Adtran 411 ONTs from critical internal networks to limit potential lateral movement in case of compromise.
  2. Access Control Enforcement: Implement strict access controls on management interfaces of ONTs, restricting access to trusted IP addresses and using VPNs or secure tunnels where possible.
  3. Monitoring and Logging: Enhance network monitoring to detect unusual traffic patterns or unauthorized access attempts targeting ONTs. Deploy intrusion detection/prevention systems (IDS/IPS) tuned for Adtran device signatures.
  4. Firmware Verification and Updates: Engage with Adtran or authorized vendors to obtain information on patches or firmware updates addressing this vulnerability. Until patches are available, consider temporary device replacement or disabling vulnerable features if feasible.
  5. Incident Response Preparedness: Develop and test incident response plans specific to network device compromise, including rapid isolation and recovery procedures.
  6. Vendor Communication: Maintain active communication channels with Adtran for timely updates and advisories.
  7. Network Device Inventory: Maintain an accurate inventory of all Adtran ONTs deployed to prioritize remediation efforts and ensure no devices are overlooked.

Description

An issue in Adtran 411 ONT vL80.00.0011.M2 allows attackers to escalate privileges via unspecified vectors.

References

Community reviews

Loading reviews…