CVE-2026-103946
Description
A flaw was found in Nessus. A remote authenticated attacker could exploit a Structured Query Language (SQL) injection vulnerability by submitting specially crafted requests to the application. Successful exploitation could lead to unauthorized data modification and information disclosure, allowing the attacker to view, alter, or delete records stored by the database.
Statement
An IMPORTANT severity Structured Query Language (SQL) injection vulnerability was found in Tenable Nessus, a third-party product that is not distributed by Red Hat. A remote authenticated attacker could exploit this flaw by submitting specially crafted requests to the Nessus application, allowing them to view, alter, or delete records stored in the Nessus database, resulting in unauthorized data modification and information disclosure. Exploitation requires valid authenticated credentials, which limits potential attackers to users who already have access to the Nessus application. Because Nessus is a third-party Tenable product, no Red Hat products are affected by this flaw. The Red Hat impact rating of IMPORTANT is consistent with the CVSS v3 base score of 8.3 assigned by both Red Hat and the upstream CVE record.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Tenable has released Nessus version 10.12.5 to address this issue; installations of Tenable Nessus should be upgraded to this fixed version in accordance with the vendor advisory (TNS-2026-26).
Understanding the Weakness (CWE)
Confidentiality,Integrity,Availability
Technical Impact: Execute Unauthorized Code or Commands
Adversaries could execute system commands, typically by changing the SQL statement to redirect output to a file that can then be executed.
Confidentiality
Technical Impact: Read Application Data
Since SQL databases generally hold sensitive data, loss of confidentiality is a frequent problem with SQL injection vulnerabilities.
Authentication
Technical Impact: Gain Privileges or Assume Identity; Bypass Protection Mechanism
If poor SQL commands are used to check user names and passwords or perform other kinds of authentication, it may be possible to connect to the product as another user with no previous knowledge of the password.
Access Control
Technical Impact: Bypass Protection Mechanism
If authorization information is held in a SQL database, it may be possible to change this information through the successful exploitation of a SQL injection vulnerability.
Integrity
Technical Impact: Modify Application Data
Just as it may be possible to read sensitive information, it is also possible to modify or even delete this information with a SQL injection attack.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.