Security readout for executives and security teams
Plain-English summary
A logged-in, non-administrative user can submit malicious report data that Tenable Security Center processes unsafely, potentially taking control of the server under its service account. Successful exploitation could expose data, alter security-management information, and disrupt service.
Executive priority
Treat as an immediate remediation priority because a low-privilege account can become server-side code execution with broad business impact. Identify exposed installations and privileged report pathways now, then follow Tenable's advisory. Escalate incident review if suspicious report or service-account activity appears.
Technical view
The flaw is in server-side report rendering and is classified as CWE-95. It is remotely reachable, requires low privileges, needs no user interaction, and can execute arbitrary code as the Security Center service account. The CVSS 3.1 score is 9.9 with changed scope and high confidentiality, integrity, and availability impact.
Likely exposure
Risk is highest where non-administrative or potentially compromised accounts can access report-generation functionality. Network accessibility increases the attack surface. The supplied affected-version value is only “0,” so the precise vulnerable release range cannot be determined from this bundle.
Exploitation context
The vulnerability requires an authenticated, non-administrative account and specially crafted report input. The bundle does not identify public exploit code, observed attacks, or CISA KEV listing; therefore, active exploitation is not established.
Researcher notes
The supplied CVSS vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Evidence supports authenticated report-rendering RCE but does not provide affected release boundaries, fixed versions, technical root-cause detail, indicators of compromise, or exploitation telemetry. Avoid interpreting the supplied version value “0” as a usable product range.
Mitigation direction
- Consult Tenable advisory TNS-2026-22 for confirmed affected versions, updates, and vendor-prescribed mitigations.
- Apply Tenable's confirmed security update after testing it in a representative environment.
- Restrict report-generation access to essential, trusted accounts until remediation is verified.
- Revoke unnecessary Security Center accounts and review low-privilege account permissions.
- Limit network access to Security Center using existing administrative access controls.
Validation and detection
- Inventory Security Center versions and builds, then compare them with Tenable advisory TNS-2026-22.
- Confirm which non-administrative roles can create or influence rendered reports.
- Review authentication and report-generation records for unusual activity around untrusted accounts.
- Examine server telemetry for unexpected processes launched by the Security Center service account.
- After updating, verify the installed build matches Tenable's documented fixed release.
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-95: 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 lookupExecution behavior lookup
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.
Open ATT&CK lookupCVE-2026-19626 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.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:L/UI:N/S:C/C:H/I:H/A:H3.16tenableCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——tenableVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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-22CVE reference, tenable · vendor-advisory
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 Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.