The audit file upload handler does not sanitize filenames, allowing shell metacharacters to flow into system command execution. This input validation failure enables command injection when chained with a related vulnerability.
Security readout for executives and security teams
Plain-English summary
A flaw in Tenable Security Center’s audit-file upload handling can let a low-privileged authenticated attacker inject operating-system commands through a crafted filename. Successful exploitation requires chaining with a related vulnerability, but could compromise data confidentiality, integrity, and availability.
Executive priority
Treat this as a high-priority remediation item because successful command execution could enable full system impact. Promptly identify Security Center deployments, confirm affected versions with Tenable, and apply vendor guidance. Escalate priority if the related vulnerability is present or suspicious upload activity is detected.
Technical view
The upload handler fails to sanitize filenames before they reach system command execution, creating CWE-78 command injection. CVSS 3.1 rates it 8.8: network-accessible, low complexity, low privileges, no user interaction, unchanged scope, and high impact across confidentiality, integrity, and availability. The necessary related vulnerability is not identified in the supplied evidence.
Likely exposure
Tenable Security Center deployments may be exposed when they fall within the vendor-defined affected versions and permit an authenticated low-privileged user to reach audit-file upload functionality. The supplied version value, “0,” is not a usable affected-version range, so exposure must be confirmed against Tenable’s advisory and local inventory.
Exploitation context
The sources describe exploitation as requiring a chain with a related vulnerability. The CVE is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation. Authentication with low privileges is reflected in the CVSS vector, but the prerequisite vulnerability and practical chain conditions remain unspecified.
Researcher notes
The central uncertainty is the incomplete affected-version data and unidentified chaining vulnerability. Avoid treating filename injection alone as independently exploitable without further vendor evidence. Defensive investigation should correlate audit-file uploads with subsequent system-process activity while preserving logs and uploaded-file metadata.
Mitigation direction
Review Tenable advisory TNS-2026-19 for affected releases, fixed versions, and vendor-approved mitigations.
Upgrade affected Security Center installations according to Tenable’s published guidance.
Restrict audit-file upload access to the minimum necessary trusted administrators.
Monitor vendor and CVE updates for details about the required related vulnerability.
Validation and detection
Inventory Security Center versions and compare them with Tenable’s authoritative affected-release information.
Confirm vendor-recommended updates or mitigations are applied to every affected deployment.
Verify only authorized accounts can access audit-file upload functionality.
Review upload and process-execution telemetry for suspicious filenames or unexpected child processes.
Check whether the unspecified related vulnerability affects the same systems.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.