Skip to main content
VulnerabilityPublished Updated

CVE-2026-2697: Tenable Security Center · Insecure Direct Object Reference

Affects Tenable Security CenterSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% 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:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
TenableSecurity CenterAffected
  • <6.8.0
Fixed in–

AI-suggested

  1. Monitor Tenable’s official channels closely for patches or updates addressing CVE-2026-2697 and apply them promptly once available.
  2. Implement strict access control policies to limit the number of users with privileges that could be exploited via the 'owner' parameter.
  3. Conduct regular audits of user permissions and roles within Tenable Security Center to ensure least privilege principles are enforced.
  4. Employ network segmentation and firewall rules to restrict access to the Security Center interface to trusted administrative networks only.
  5. Enable detailed logging and monitoring of Security Center activities, particularly changes involving ownership or privilege escalation attempts, to detect suspicious behavior early.
  6. Consider additional compensating controls such as multi-factor authentication (MFA) for all users with elevated privileges to reduce the risk of credential compromise.
  7. Educate administrators and security personnel about the vulnerability and the importance of vigilance regarding unusual access patterns or privilege changes.
  8. If possible, temporarily restrict or disable features involving the 'owner' parameter until a patch is applied, minimizing the attack surface.

Description

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

References

Community reviews

Loading reviews…