dbcve.org
NessusApplication · Tenable

CVE-2026-57587

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 10.12.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A SQL injection vulnerability in Nessus allows a remote, unauthenticated attacker who controls reverse DNS records for a scanned host to inject malicious SQL into the scan results database, potentially enabling exfiltration of scan-result data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in Tenable Nessus allows remote, unauthenticated attackers who control reverse DNS records for a scanned host to inject malicious SQL queries into the scan results database, potentially enabling exfiltration of sensitive scan-result data.

MitigationImplement strict access controls on DNS record management, validate DNS responses before using them in SQL queries, apply vendor patches when available, and consider network segmentation to limit exposure of the Nessus backend database.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NessusApplication
Affected:< 10.12.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Nessus version
    Run 'nessuscli --version' or check the About page in the Nessus web interface to determine the exact version number
    Affected if The installed version is lower than 10.12.1 (e.g., 10.x.y where y < 1, or any version in the 8.x or 9.x line)
  2. Identify if reverse DNS lookups are enabled in scan policies
    Review active and scheduled scan policies in the Nessus web interface under 'Policies' to see if 'Reverse DNS Lookups' or similar DNS resolution options are enabled
    Affected if Any scan policy has reverse DNS resolution or PTR record lookup features enabled, as this allows Nessus to process attacker-controlled DNS data
  3. Determine if Nessus scans targets where third parties may control reverse DNS
    Review the target list of scheduled or active scans, specifically looking for IP ranges that belong to cloud providers, hosting companies, or networks where users outside your organization can register PTR records
    Affected if Nessus is configured to scan IP addresses for which external parties can set reverse DNS records (common with cloud platforms and dynamic IP ranges)
  4. Assess Nessus network exposure
    Verify network access to the Nessus server port (default 8834) from untrusted networks using 'netstat -an | grep 8834' or firewall rules review
    Affected if The Nessus web interface (port 8834) is accessible from networks outside your trusted internal environment without authentication barriers

You are affected if Nessus version is below 10.12.1 AND you perform scans with reverse DNS resolution enabled against targets where external parties can control PTR records.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.12.1 or later
Fixed in 10.12.1
Interim mitigation

Implement strict access controls on DNS record management, validate DNS responses before using them in SQL queries, apply vendor patches when available, and consider network segmentation to limit exposure of the Nessus backend database.

Recommended fix High confidence

Nessus 10.12.1

  1. 1. Back up your current Nessus installation, including the scan results database and configuration files.
  2. 2. Download Nessus version 10.12.1 from the official Tenable download page (www.tenable.com/products/nessus).
  3. 3. Stop the Nessus service before performing the upgrade.
  4. 4. Install Nessus 10.12.1 using the appropriate installer for your operating system.
  5. 5. Start the Nessus service after installation completes.
  6. 6. Verify the upgrade by checking the Nessus version in the web interface (Help > About Nessus).
  7. 7. Verify that existing scan results and configurations are intact.
Caveat Standard upgrade considerations apply - back up data before upgrading; review Tenable upgrade documentation for platform-specific requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nessus Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57587 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data