dbcve.org
Identity ExposureApplication · Tenable

CVE-2026-13007

HIGH · 7.5 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 3.93.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Tenable Identity Exposure contains multiple unauthenticated API endpoints under /w/api/* that expose sensitive application configuration data including cleartext LDAP credentials, SAML configuration, user accounts, and directory settings to unauthenticated remote attackers. Affected responses are served with Cache-Control: public headers and without Vary: Cookie, allowing reverse proxies and CDNs to cache and serve sensitive data to unauthenticated users even after authentication is applied.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Tenable Identity Exposure has unauthenticated API endpoints under /w/api/* that expose sensitive configuration including cleartext LDAP credentials, SAML settings, user accounts, and directory data to remote attackers. Additionally, responses include Cache-Control: public headers without Vary: Cookie, causing reverse proxies and CDNs to cache and serve this sensitive data to subsequent unauthenticated users even after authentication is applied.

MitigationImmediately restrict /w/api/* endpoints to authenticated users only, change Cache-Control headers to no-store/private, add Vary: Cookie, and rotate any exposed LDAP credentials. Audit and purge cached sensitive data from reverse proxies and CDNs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Identity ExposureApplication
Affected:< 3.93.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Tenable Identity Exposure installation and version
    Locate the Tenable Identity Exposure installation and determine the installed version by checking the application or its configuration files. Compare the installed version against any known affected version ranges provided by Tenable.
    Affected if The installed version falls within the affected version range.
  2. Test unauthenticated access to /w/api/* endpoints
    Using a web browser or curl command, attempt to access https://<tenable_identity_exposure_host>/w/api/* endpoints without providing any authentication credentials. Check if the server returns HTTP 200 responses instead of redirecting to a login page or returning 401/403.
    Affected if The /w/api/* endpoints return successful responses (HTTP 200) to unauthenticated requests.
  3. Inspect API responses for sensitive configuration data
    Examine the responses from /w/api/* endpoints for cleartext LDAP credentials, SAML settings, user account information, or directory data. Search for fields such as 'password', 'ldap', 'saml', 'credentials', or similar sensitive configuration keys in the JSON or HTML responses.
    Affected if The API responses contain cleartext LDAP passwords, SAML configuration, user accounts, or other sensitive directory data without requiring authentication.
  4. Check Cache-Control header configuration
    Inspect the HTTP response headers from /w/api/* endpoints. Look specifically for 'Cache-Control: public' headers. Also check whether the 'Vary' header includes 'Cookie' or is missing entirely.
    Affected if Responses include 'Cache-Control: public' without a 'Vary: Cookie' header, indicating the sensitive data can be cached by proxies and CDNs.
  5. Verify caching by downstream proxies or CDNs
    If a reverse proxy (like nginx, Apache) or CDN is in front of Tenable Identity Exposure, examine its configuration and cached responses. Attempt to access the /w/api/* endpoints and check if subsequent requests (including from different IP addresses) receive cached sensitive data.
    Affected if Cached responses from /w/api/* endpoints containing sensitive data are served to subsequent unauthenticated users.

The environment is affected if /w/api/* endpoints are accessible without authentication and expose sensitive data such as cleartext LDAP credentials, or if responses contain Cache-Control: public without Vary: Cookie, enabling caching of sensitive information by proxies or CDNs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 3.93.5 or later
Fixed in 3.93.5
Interim mitigation

Immediately restrict /w/api/* endpoints to authenticated users only, change Cache-Control headers to no-store/private, add Vary: Cookie, and rotate any exposed LDAP credentials. Audit and purge cached sensitive data from reverse proxies and CDNs.

Fix this in Identity Exposure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13007 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data