LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2697: Indirect Object Reference (IDOR) in Security Center

An Indirect Object Reference (IDOR) in Security Center allows an authenticated remote attacker to escalate privileges via the 'owner' parameter.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-2697 is a medium-severity access control flaw in Tenable Security Center. A logged-in remote attacker could abuse an exposed “owner” parameter to gain privileges they should not have. Business impact depends on how broadly Security Center accounts are issued and what elevated privileges could change or access.

Executive priority

Treat as a planned but timely remediation item. It requires authentication, lowering urgency versus unauthenticated flaws, but privilege escalation in a security management platform can affect sensitive vulnerability data and operational integrity.

Technical view

The issue is an Indirect Object Reference / authorization weakness, mapped to CWE-639. The CVSS 3.1 score is 6.3 with network attack vector, low complexity, low privileges required, no user interaction, and limited confidentiality, integrity, and availability impact. The affected product is listed as Tenable Security Center; version detail in the provided record is not sufficiently clear.

Likely exposure

Exposure is most relevant where Tenable Security Center is reachable by authenticated users, including lower-privileged internal, VPN, or delegated accounts. The record does not indicate unauthenticated exploitation or broad internet-scale scanning risk.

Exploitation context

The CVE states an authenticated remote attacker can escalate privileges via the “owner” parameter. The source bundle does not show CISA KEV listing, active exploitation, public exploit availability, or detailed attacker procedures.

Researcher notes

Evidence is limited to the CVE record and Tenable advisory reference. The provided affected version value is “0,” which is not enough to determine exact vulnerable releases. Avoid assuming fixed versions or mitigations until confirmed in Tenable’s advisory.

Mitigation direction

  • Review Tenable advisory TNS-2026-07 for affected versions and vendor-approved fixes.
  • Apply any Tenable-provided Security Center update or workaround when confirmed applicable.
  • Restrict Security Center access to trusted networks and necessary users.
  • Review account roles and remove unnecessary low-privileged or stale accounts.

Validation and detection

  • Inventory Tenable Security Center deployments and versions.
  • Check whether deployments match Tenable advisory TNS-2026-07 applicability.
  • Review Security Center audit logs for unusual owner or privilege-related changes.
  • Confirm least-privilege role assignments for all Security Center users.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-639: 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 lookup
cve · low confidence lookup

CVE-2026-2697 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2026-2697Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TenableSecurity Center0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.