{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-8864 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8864 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8864 is a medium-severity vulnerability in YugabyteDB Anywhere, published on 11 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8864 and fix it if it is affected.\n\nWhat it is: CVE-2025-8864 is a medium-severity vulnerability in YugabyteDB Anywhere, published on 11 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-8864 in the wild and no public exploit code.\n\nAffected product: YugabyteDB Anywhere. 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-2025-8864/ (Markdown: https://insights.sbomify.com/CVE-2025-8864/index.md)","id":"CVE-2025-8864","markdown":"https://insights.sbomify.com/CVE-2025-8864/index.md","name":"CVE-2025-8864","record":{"aliases":["GHSA-776c-ggqp-xjxg"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"YugabyteDB Anywhere","requires_auth":"high_privilege","summary":"Attackers can read exposed Shared Access Signature tokens from backup configuration responses and logs, potentially compromising cloud storage access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Yugabyte","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Shared Access Signature token is not masked in the backup configuration response and is also exposed in the yb_backup logs","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":"Information disclosure in YugabyteDB Anywhere","id":"CVE-2025-8864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in YugabyteDB","id":"CVE-2025-8865"},"packages":[],"prev":{"headline":"Information disclosure in YugabyteDB","id":"CVE-2025-8863"},"products":["YugabyteDB Anywhere"],"published":"2025-08-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-08-11","vendors":["YugabyteDB Inc"]},"summary":"Attackers can read exposed Shared Access Signature tokens from backup configuration responses and logs, potentially compromising cloud storage access.","url":"https://insights.sbomify.com/CVE-2025-8864/"}