CVE-2026-57588: Tenable Nessus SQL injection in scan result import

CVE-2026-57588 · Severity: low · CVSS 3.3 · Published 2026-06-25

A vulnerability in the Nessus vulnerability scanner could allow an attacker to steal sensitive scan data. By tricking a legitimate user into importing a specially crafted, malicious scan result file, an attacker can execute unauthorized database commands. This could lead to the unauthorized exposure of internal security scan information, though it requires manual interaction from a user with import privileges.

Technologies: Tenable Nessus. Vendors: Tenable.

Quick answers

Is CVE-2026-57588 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-57588 being exploited in the wild.
How severe is CVE-2026-57588?
Low severity, with a CVSS score of 3.3, published 25 June 2026.
Which products and versions are affected?
Tenable Nessus < 10.12.1.
Is there a fix for CVE-2026-57588?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-57588 attacked?
It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-57588?
Check whether you run Tenable Nessus at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A SQL injection vulnerability (CWE-89) exists in Tenable Nessus due to improper neutralization of special elements within scan result files. An attacker can exploit this by crafting a malicious scan result file and social engineering a privileged user into importing it into the Nessus console. Upon import, the malicious SQL commands are executed against the underlying scan results database. This could allow an attacker to exfiltrate sensitive scan data. The vulnerability is addressed in Nessus version 10.12.1.

Affected products

  • Tenable Nessus < 10.12.1

Timeline

  • 2026-06-25: disclosed
  • 2026-06-25: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.