Skip to content
Fencer Intel
high 8.1

CVE-2025-52690 in the critical feed json

Command Injection Vulnerability in the OmniAccess Stellar over UDP Service

published last yr. modified 4mo ago also EUVD-2025-21585

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
14.4%
EPSS 14.4% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

Successful exploitation of the vulnerability could allow an attacker to execute arbitrary commands as root, potentially leading to the loss of confidentiality, integrity, availability, and full control of the access point.

Is CVE-2025-52690 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 Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

14.40% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • jro.sg https://jro.sg/CVEs/CVE-2025-52690/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Alcatel-Lucent OmniAccess Stellar Products

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

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.