Security readout for executives and security teams
Plain-English summary
A logged-in user without administrative privileges may abuse Tenable Security Center’s ticketing REST API to read or alter sensitive appliance database information. Because exploitation is remote, low-complexity, and requires no user interaction, a compromised low-privilege account could create serious confidentiality, integrity, and availability consequences.
Executive priority
Treat this as an urgent remediation and exposure-review item. Prioritize internet-accessible or broadly reachable deployments and environments containing sensitive findings, credentials, or asset data. Do not delay solely because authentication is required; ordinary account compromise could provide the necessary access.
Technical view
CVE-2026-64877 is an authenticated SQL injection vulnerability in the Security Center ticketing REST API. The supplied CVSS 4.0 score is 9.4, with network access, low complexity, low privileges, no user interaction, and high impacts across vulnerable and subsequent systems. The bundle classifies it as CWE-20, but provides no endpoint, parameter, or root-cause details.
Likely exposure
Exposure requires a Tenable Security Center deployment, a valid non-admin account, and reachable access to the affected ticketing REST API. The supplied affected-version value is only “0,” which is insufficient to determine actual vulnerable releases. Confirm product versions and applicability directly against Tenable’s advisory.
Exploitation context
The source bundle does not establish active exploitation, and CVE-2026-64877 is not marked as included in CISA KEV. Authentication reduces exposure compared with an unauthenticated flaw, but compromised, malicious, or over-permissioned non-admin accounts could satisfy the stated prerequisite.
Researcher notes
Important technical details remain unavailable in the supplied bundle, including affected release ranges, fixed versions, vulnerable parameters, evidence of exploitation, and detection indicators. The affected-version entry “0” appears non-actionable. Researchers should use Tenable’s advisory and CVE records to establish scope without assuming undocumented endpoints or fixes.
Mitigation direction
- Review Tenable advisory TNS-2026-19 for affected releases and vendor-approved remediation.
- Apply the vendor-provided update or mitigation once applicability is confirmed.
- Restrict ticketing REST API access to trusted networks and necessary users.
- Disable or remove unnecessary accounts and rotate credentials suspected of compromise.
- Monitor vendor guidance because the supplied bundle does not name a fixed version.
Validation and detection
- Inventory Tenable Security Center deployments, versions, and exposed ticketing REST API paths.
- Compare every deployed version with the affected-release information in TNS-2026-19.
- Review API and authentication logs for unusual ticketing requests from non-admin accounts.
- Investigate unexpected database access, data changes, service disruption, or downstream activity.
- After remediation, confirm the installed version and repeat approved defensive API testing.
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-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-64877 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.4 (4.0)
- Known Exploited
- No
- Published
Vector: 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
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:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——tenableCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N25.8tenableVulnerability 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
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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-19CVE 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 Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.