CVE-2025-40902: Nozomi Networks Guardian · Cross-site Scripting
Affects Nozomi Networks GuardianSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium : upgrade to 26.1.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:L/VI:L/VA:L/SC:L/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 19 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade Guardian and CMC to 26.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Nozomi NetworksGuardian | Affected
| Fixed in
|
| Nozomi NetworksCMC | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, limit administrative access to trusted users only and monitor for suspicious activity involving user creation and group deletion. The existing input validation and Content Security Policy provide partial mitigation.
Description
A Stored HTML Injection vulnerability was discovered in the Users functionality due to improper validation of an input parameter. An authenticated user with administrative privileges can create a malicious user whose username contains HTML tags. When a victim attempts to delete a group containing the affected user, the injected HTML renders in their browser, enabling phishing and possibly open redirect attacks. Full XSS exploitation and direct information disclosure are prevented by the existing input validation and Content Security Policy configuration.