A command injection vulnerability exists in Security Center where a remote, unauthenticated attacker could exploit this issue to execute arbitrary commands on the underlying operating system with the privileges of the service account.
Security readout for executives and security teams
Plain-English summary
Tenable Security Center may allow a remote attacker to run operating-system commands with the service account’s permissions. Successful exploitation could expose sensitive data, alter the system, or disrupt service. The supplied records do not clearly identify affected releases or a fixed version.
Executive priority
Treat as an immediate remediation priority, especially where Security Center is accessible from untrusted networks. Require owners to establish version exposure, restrict access, apply vendor guidance, and investigate suspicious service-account activity.
Technical view
CVE-2026-19682 is a CWE-78 command-injection flaw rated CVSS 9.9. The description says exploitation is remote and unauthenticated, while the CVSS vector specifies low privileges required. Commands execute with service-account privileges, with potentially high confidentiality, integrity, and availability impact.
Likely exposure
Security Center deployments reachable by untrusted networks warrant immediate review. The affected-version entry contains only "0," which is insufficient for determining actual vulnerable releases. Confirm exposure against Tenable advisory TNS-2026-22 and the installed product version.
Exploitation context
No supplied source reports active exploitation, and the KEV flag is false. This is not proof that exploitation is absent. The vulnerability’s network reachability, low complexity, and command-execution impact make exposed deployments attractive targets.
Researcher notes
The supplied metadata has two important gaps: the affected version is recorded only as "0," and no fixed release is named. It also conflicts on authentication requirements: the description says unauthenticated, but CVSS specifies PR:L. Use TNS-2026-22 as the authoritative clarification source.
Mitigation direction
Review Tenable advisory TNS-2026-22 for confirmed affected and fixed releases.
Apply Tenable’s supported update or mitigation after validating deployment compatibility.
Restrict Security Center access to trusted administrative networks until remediation is confirmed.
Monitor the Security Center service account for unexpected processes and activity.
Validation and detection
Inventory all Security Center instances, versions, and network exposure.
Compare installed versions with the affected range in TNS-2026-22.
Confirm remediation status using Tenable-supported version or configuration evidence.
Review relevant application, operating-system, and identity logs for suspicious service-account activity.
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.
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.