CVE-2026-103948: Inconsistent length handling in Tenable Nessus
CVE-2026-103948 is an improper handling of inconsistent length values vulnerability in Tenable Nessus versions earlier than 10.12.5. An authenticated, privileged attacker could exploit the flaw to compromise Nessus confidentiality, integrity, or availability. The affected function and specific triggering input are not identified.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation could compromise the confidentiality, integrity, or availability of Nessus. The extent of data exposure, modification, or service disruption is not specified for this CVE.
Mitigation
If you can’t patch tonight, do this now.
Pending upgrade, restrict Nessus administrative and privileged accounts to trusted personnel, enforce least privilege and strong authentication, limit access to management interfaces, and monitor for anomalous authenticated activity, unexpected data changes, and service instability. These are interim risk-reduction measures; no vulnerability-specific vendor workaround is identified.
Remediation
Patch, then assume compromise.
Upgrade Tenable Nessus to version 10.12.5 or a later fixed release using vendor-provided installation packages. Version 10.12.5 includes the fix announced in Tenable security bulletin TNS-2026-26 on October 1, 2026.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-103948 exploited in the wild?
- As of Oct 2, 2026, Mallory has no reports of CVE-2026-103948 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-103948?
- As of Oct 2, 2026, Mallory has found no public exploit for CVE-2026-103948.
- Is there a patch for CVE-2026-103948?
- Upgrade Tenable Nessus to version 10.12.5 or a later fixed release using vendor-provided installation packages. Version 10.12.5 includes the fix announced in Tenable security bulletin TNS-2026-26 on October 1, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.