Security readout for executives and security teams
Plain-English summary
A remote attacker could gain elevated control of a vulnerable Tenable Sensor Proxy by persuading an operator to connect a sensor to an attacker-controlled host. Successful exploitation could expose sensitive data, alter systems, or disrupt service. The issue is critical, but it requires operator interaction.
Executive priority
Treat remediation as urgent because successful exploitation could provide elevated code execution with broad confidentiality, integrity, and availability impact. Prioritize environments where operators frequently configure sensor destinations or receive connection instructions from external channels. Confirm inventory and deploy version 1.4.2 promptly.
Technical view
CVE-2026-18667 is a CWE-94 code-execution vulnerability in Tenable Sensor Proxy. It has CVSS 3.1 score 9.6 and permits network-based, low-complexity exploitation without prior privileges, but requires user interaction. Tenable identifies Sensor Proxy 1.4.2 as the fixed version. The supplied affected-version data is incomplete.
Likely exposure
Exposure exists where an affected Sensor Proxy can be directed to an attacker-controlled host and an operator can be induced to approve or initiate that connection. Internet exposure alone is not established as sufficient. The source bundle does not provide a reliable affected-version range.
Exploitation context
The CVE is not listed in the supplied CISA KEV data, and the sources provide no evidence of active exploitation. Exploitation depends on influencing an operator, which reduces opportunistic risk but remains credible through social engineering, endpoint substitution, or compromised operational instructions.
Researcher notes
The supplied version entry lists only “0,” which is insufficient to establish the full affected range. Researchers should rely on Tenable’s advisory for authoritative applicability. The attack crosses a trust boundary and requires operator interaction. No exploit method, indicators of compromise, or active-exploitation evidence are included in the source bundle.
Mitigation direction
- Upgrade Tenable Sensor Proxy to version 1.4.2, identified by Tenable as the fixed release.
- Until upgraded, prevent operators from connecting sensors to unverified or externally supplied hosts.
- Restrict sensor connection destinations to approved infrastructure where operationally feasible.
- Brief operators to reject unsolicited connection endpoints and independently verify destination ownership.
Validation and detection
- Inventory all Tenable Sensor Proxy deployments and record their installed versions.
- Confirm every deployment runs version 1.4.2 or a vendor-confirmed non-affected release.
- Review configured connection destinations and verify that each host is authorized and controlled.
- Investigate unexpected destination changes or connections to untrusted hosts around operator activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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.
Open ATT&CK lookupCVE-2026-18667 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86tenableCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——tenableVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.tenable.com/security/tns-2026-21CVE reference, tenable
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.