Skip to main content
CVE-2025-40887VulnerabilityPublished

CVE-2025-40887: Nozomi Networks Guardian · SQL Injection

Affects Nozomi Networks GuardianSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Nozomi Networks GuardianAffected
  • =0
Fixed in–

AI-suggested

1. Implement strict input validation and sanitization on all user-supplied parameters in the Alert functionality to prevent SQL injection. 2. Apply the principle of least privilege by reviewing and restricting database user permissions used by the Guardian application to limit the scope of data accessible via SQL queries. 3. Monitor and audit authenticated user activities within the Guardian application to detect unusual query patterns or access attempts. 4. Segregate the Guardian management interface and database access to trusted networks only, reducing exposure to unauthorized users. 5. Engage with Nozomi Networks for official patches or updates addressing this vulnerability and apply them promptly once available. 6. Consider deploying Web Application Firewalls (WAF) or database activity monitoring tools that can detect and block SQL injection attempts. 7. Conduct regular security assessments and penetration testing focused on OT security tools to identify similar vulnerabilities proactively. 8. Educate users with access to Guardian about secure usage practices and the risks of SQL injection attacks.

Description

A SQL Injection vulnerability was discovered in the Alert functionality due to improper validation of an input parameter. An authenticated user with limited privileges can execute arbitrary SELECT SQL statements on the DBMS used by the web application, potentially exposing unauthorized data.

References

Community reviews

Loading reviews…