{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-8863 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8863 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8863 is a high-severity vulnerability in YugabyteDB, published on 11 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8863 and fix it if it is affected.\n\nWhat it is: CVE-2025-8863 is a high-severity vulnerability in YugabyteDB, published on 11 Aug 2025. 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-2025-8863 in the wild and no public exploit code.\n\nAffected product: YugabyteDB. 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-8863/ (Markdown: https://insights.sbomify.com/CVE-2025-8863/index.md)","id":"CVE-2025-8863","markdown":"https://insights.sbomify.com/CVE-2025-8863/index.md","name":"CVE-2025-8863","record":{"aliases":["GHSA-58pc-g9rc-gr6v"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"YugabyteDB database","requires_auth":"none","summary":"Attackers can intercept sensitive diagnostic data transmitted over unencrypted HTTP connections in YugabyteDB.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Yugabyte","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"YugabyteDB diagnostic information was transmitted over HTTP, which could expose sensitive data during transmission","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in YugabyteDB","id":"CVE-2025-8863","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":"Information disclosure in YugabyteDB Anywhere","id":"CVE-2025-8864"},"packages":[],"prev":{"headline":"Information disclosure in YugabyteDB","id":"CVE-2025-8862"},"products":["YugabyteDB"],"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 intercept sensitive diagnostic data transmitted over unencrypted HTTP connections in YugabyteDB.","url":"https://insights.sbomify.com/CVE-2025-8863/"}