{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-13007 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13007 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-13007 is a high-severity vulnerability in Tenable Identity Exposure, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-13007 and fix it if it is affected.\n\nWhat it is: CVE-2026-13007 is a high-severity vulnerability in Tenable Identity Exposure, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-13007 in the wild and no public exploit code.\n\nAffected product: Tenable Identity Exposure. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-13007/ (Markdown: https://insights.sbomify.com/CVE-2026-13007/index.md)","id":"CVE-2026-13007","markdown":"https://insights.sbomify.com/CVE-2026-13007/index.md","name":"CVE-2026-13007","record":{"aliases":["GHSA-rqcc-h287-275c"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity Exposure","requires_auth":"none","summary":"Unauthenticated attackers can access sensitive configuration data, including cleartext credentials, via insecurely cached public API endpoints.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"tenable","cpe":[{"product":"identity_exposure","vendor":"tenable"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Insecure Public Caching on REST API Endpoints in Tenable Identity Exposure","id":"CVE-2026-13007","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"AI Copilot \u003c= 1.5.4 - Authenticated (Subscriber+) SQL Injection via 'order[0][dir]' Parameter","id":"CVE-2026-13009"},"packages":[],"prev":{"headline":"Incomplete protection against CVE-2025-11226","id":"CVE-2026-13006"},"products":["Tenable Identity Exposure"],"published":"2026-06-23","related":[{"cvss_score":7.6,"headline":"Formula Injection Vulnerability","id":"CVE-2024-3232","kev_date_added":null,"published":"2024-07-16"},{"cvss_score":7.3,"headline":"DLL Injection in Tenable Identity Exposure Secure Relay","id":"CVE-2024-1683","kev_date_added":null,"published":"2024-02-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["tenable"]},"summary":"Unauthenticated attackers can access sensitive configuration data, including cleartext credentials, via insecurely cached public API endpoints.","url":"https://insights.sbomify.com/CVE-2026-13007/"}