Tenable Nessus 10.12.5 Fixes Nine Vulnerabilities
Tech GuruQuick Answer
Tenable Nessus 10.12.5 fixes nine vulnerabilities affecting 10.12.4 and earlier. The highest score, CVSS v3.1 9.1 for CVE-2026-103947, concerns insufficient integrity verification of downloaded content and requires an authenticated privileged attacker. Install the Nessus application update; current scan plugins alone do not establish that the scanner software is fixed.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Tenable Nessus 10.12.4 and earlier, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-10-02 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Tenable Nessus 10.12.4 and earlier |
|---|---|
| Advisory | TNS-2026-26 |
| CVEs | CVE-2026-103946, CVE-2026-103947, CVE-2026-103948, CVE-2026-103950, CVE-2026-103951, CVE-2026-103952, CVE-2026-103953, CVE-2026-103954, CVE-2026-103955 |
| Authoritative release date | 2026-10-01 (Tenable date; no time stated) |
| Authority revision date | Initial publication; no later material revision stated when verified |
| Affected versions | Tenable Nessus 10.12.4 and earlier. |
| Fixed version | Tenable Nessus 10.12.5 |
| CVSS base score | 2.7–9.1 (official CVSS v3.1 range) |
| CVSS severity | Low to Critical |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The set includes authenticated SQL injection, downloaded-content integrity checks, memory-handling flaws, information disclosure and denial of service. The SQL injection entry requires an authenticated user; the other eight entries specify an authenticated privileged attacker. These conditions matter when prioritizing exposed management interfaces and administrative accounts.
What To Validate Now
- Inventory. Record scanner hosts, application versions, management exposure, registration, scan schedules and credential owners. Do not infer that a plugin feed date or another Tenable product version identifies the Nessus build.
- Establish applicability. Identify self-managed Nessus scanners and confirm whether the installed version is 10.12.4 or earlier. Do not infer scope for another Tenable product.
- Remediate. Install Tenable Nessus 10.12.5 through the supported update channel and follow current Tenable upgrade guidance.
- Validate. Confirm the running scanner reports 10.12.5 or a supported superseding fix, registration and plugin updates succeed, and a small authorized scan completes using the expected policy and credentials. Resume schedules deliberately to avoid duplicate or unexpectedly broad scans.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Preserve configuration and scan history through the supported upgrade process, protect stored scanning credentials, and coordinate ongoing jobs before restarting. A high severity score is not evidence that a scanner has already been compromised.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
