{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-75839 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-75839 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75839 is a medium-severity vulnerability in ArcadeData arcadedb, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-75839 and fix it if it is affected.\n\nWhat it is: CVE-2026-75839 is a medium-severity vulnerability in ArcadeData arcadedb, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-75839 in the wild and no public exploit code.\n\nAffected product: ArcadeData arcadedb. 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-75839/ (Markdown: https://insights.sbomify.com/CVE-2026-75839/index.md)","id":"CVE-2026-75839","markdown":"https://insights.sbomify.com/CVE-2026-75839/index.md","name":"CVE-2026-75839","record":{"aliases":["GHSA-5g3q-578q-gf3m","GHSA-79wq-w74x-74ch"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"ArcadeDB server","requires_auth":"low_privilege","summary":"Authenticated users in ArcadeDB HA clusters can access cluster endpoints to enumerate database names and metadata, leading to cross-database information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"ArcadeDB (com.arcadedb:arcadedb-server) versions \u003c= 26.7.3 contain an insecure direct object reference (IDOR) vulnerability in the Raft cluster-info endpoints (GetClusterHandler and PostBootstrapStateHandler), which authenticate but do not authorize access. On an ArcadeDB HA cluster (only reachable when arcadedb.ha.enabled is set and the ha-raft module is loaded), any authenticated user — including one granted access to only one database or none — can enumerate the full server database registry and retrieve per-database metadata such as database names, last transaction IDs, bootstrap fingerprints, and peer/leader cluster topology, resulting in cross-database information disclosure. Fixed in 26.8.1.","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":"ArcadeDB before 26.8.1 Information Disclosure via Cluster Endpoints","id":"CVE-2026-75839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"ArcadeDB before 26.8.1 Arbitrary File Read via Unescaped Regex","id":"CVE-2026-75840"},"packages":[],"prev":{"headline":"DOMPurify before 3.4.13 Cross-Site Scripting via IN_PLACE hook","id":"CVE-2026-75838"},"products":["arcadedb"],"published":"2026-08-18","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":"2026-08-18","vendors":["ArcadeData"]},"summary":"Authenticated users in ArcadeDB HA clusters can access cluster endpoints to enumerate database names and metadata, leading to cross-database information disclosure.","url":"https://insights.sbomify.com/CVE-2026-75839/"}