Skip to main content
CVE-2025-40888VulnerabilityPublished

CVE-2025-40888: 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. Restrict CLI access strictly to trusted and trained personnel, implementing role-based access controls to minimize the number of users with privileges to interact with the CLI. 2. Monitor and audit CLI usage and database query logs for unusual or unauthorized SELECT queries that could indicate exploitation attempts. 3. Implement network segmentation to isolate the Nozomi Guardian management interfaces from general user networks, reducing exposure to potential attackers. 4. Employ input validation and sanitization at the application level where possible, and request the vendor to provide or prioritize a patch addressing the SQL injection flaw. 5. Use multi-factor authentication (MFA) for all users accessing the system to reduce the risk of compromised credentials being used to exploit this vulnerability. 6. Conduct regular security assessments and penetration tests focusing on OT security tools to identify similar vulnerabilities proactively. 7. Stay informed on vendor advisories and apply patches promptly once available.

Description

A SQL Injection vulnerability was discovered in the CLI 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…