Skip to main content
Mallory
UnratedVulnerability

CVE-2026-103948: Inconsistent length handling in Tenable Nessus

Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-103948CWE-130

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.