{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-6392 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6392 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6392 is a low-severity vulnerability in Tanium Threat Response, published on 22 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6392 and fix it if it is affected.\n\nWhat it is: CVE-2026-6392 is a low-severity vulnerability in Tanium Threat Response, published on 22 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6392 in the wild and no public exploit code.\n\nAffected product: Tanium Threat Response. 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-6392/ (Markdown: https://insights.sbomify.com/CVE-2026-6392/index.md)","id":"CVE-2026-6392","markdown":"https://insights.sbomify.com/CVE-2026-6392/index.md","name":"CVE-2026-6392","record":{"aliases":["GHSA-w6jx-7fh4-vggr"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Tanium Threat Response","requires_auth":"high_privilege","summary":"An attacker can access sensitive information in Tanium Threat Response, requiring a patch to mitigate the data exposure risk.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Tanium","cpe":[{"product":"threat_response","vendor":"tanium"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Tanium addressed an information disclosure vulnerability in Threat Response.","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":"Tanium addressed an information disclosure vulnerability in Threat Response.","id":"CVE-2026-6392","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":"BetterDocs \u003c= 4.3.11 - Missing Authorization to Authenticated (Subscriber+) Unauthorized AI API Usage","id":"CVE-2026-6393"},"packages":[],"prev":{"headline":"Cross-site request forgery in Sentence To SEO (keywords, description and tags)","id":"CVE-2026-6391"},"products":["Threat Response"],"published":"2026-04-22","related":[{"cvss_score":4.9,"headline":"Tanium addressed an information disclosure vulnerability in Threat Response.","id":"CVE-2025-15329","kev_date_added":null,"published":"2026-02-05"},{"cvss_score":4.9,"headline":"Tanium addressed an information disclosure vulnerability in Threat Response.","id":"CVE-2025-15332","kev_date_added":null,"published":"2026-02-05"},{"cvss_score":4.3,"headline":"Tanium addressed an information disclosure vulnerability in Threat Response.","id":"CVE-2025-15333","kev_date_added":null,"published":"2026-02-05"},{"cvss_score":4.3,"headline":"Tanium addressed an information disclosure vulnerability in Threat Response.","id":"CVE-2025-15334","kev_date_added":null,"published":"2026-02-05"},{"cvss_score":4.3,"headline":"Tanium addressed an information disclosure vulnerability in Threat Response.","id":"CVE-2025-15335","kev_date_added":null,"published":"2026-02-05"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["Tanium"]},"summary":"An attacker can access sensitive information in Tanium Threat Response, requiring a patch to mitigate the data exposure risk.","url":"https://insights.sbomify.com/CVE-2026-6392/"}