CVE-2026-2630: Tenable Security Center · OS Command Injection
Affects Tenable Security CenterSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TenableSecurity Center | Affected
| Fixed in– |
AI-suggested
Until an official patch is released, organizations should implement the following mitigations: 1) Restrict access to Tenable Security Center to trusted administrators only, enforcing strong authentication mechanisms such as multi-factor authentication (MFA). 2) Monitor and audit all administrative activities and login attempts for suspicious behavior. 3) Employ network segmentation to isolate the Security Center server from less trusted network zones. 4) Use application-layer firewalls or intrusion detection/prevention systems to detect and block anomalous command injection attempts. 5) Regularly back up Security Center configurations and data to enable recovery in case of compromise. 6) Stay informed about vendor updates and apply patches immediately once available. 7) Conduct internal penetration testing focusing on command injection vectors to identify potential exploitation paths. These steps go beyond generic advice by emphasizing access control hardening, monitoring, and network isolation tailored to the specific threat.
Description
A Command Injection vulnerability exists where an authenticated, remote attacker could execute arbitrary code on the underlying server where Tenable Security Center is hosted.