Quick answers
- Is CVE-2026-13007 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13007 being exploited in the wild.
- How severe is CVE-2026-13007?
- High severity, with a CVSS score of 7.5, published 23 June 2026.
- Which products and versions are affected?
- Tenable Identity Exposure < 3.93.5.
- Is there a fix for CVE-2026-13007?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-13007 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-13007?
- Check whether you run Tenable Identity Exposure at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Tenable Identity Exposure versions prior to 3.93.5 suffer from missing authentication on several API endpoints located under the /w/api/* path. This vulnerability allows a remote, unauthenticated attacker to query these endpoints and retrieve sensitive configuration data, including cleartext LDAP credentials, SAML configurations, and directory settings. Additionally, the application improperly uses 'Cache-Control: public' headers without a 'Vary: Cookie' header, which can cause downstream reverse proxies or CDNs to cache these sensitive responses and serve them to other unauthenticated users. The issue is categorized under CWE-306 (Missing Authentication for Critical Function) and CWE-524 (Use of Cache Containing Sensitive Information). Users should upgrade to version 3.93.5 or later to remediate these risks.
Affected products
- Tenable Identity Exposure < 3.93.5
Timeline
- 2026-06-23: disclosed
- 2026-06-23: advisory