{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70829 exists.","fix":"No fix has been published for CVE-2025-70829 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70829 is a medium-severity vulnerability in n/a, published on 17 Feb 2026. 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-70829 and fix it if it is affected.\n\nWhat it is: CVE-2025-70829 is a medium-severity vulnerability in n/a, published on 17 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70829 exists.\n\nAffected product: n/a. 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-70829/ (Markdown: https://insights.sbomify.com/CVE-2025-70829/index.md)","id":"CVE-2025-70829","markdown":"https://insights.sbomify.com/CVE-2025-70829/index.md","name":"CVE-2025-70829","record":{"aliases":["GHSA-m5mm-m787-fp43"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Datart BI tool","requires_auth":"low_privilege","summary":"Authenticated attackers can access sensitive data in Datart by exploiting a custom H2 JDBC connection string vulnerability.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"datart","vendor":"running-elephant"}],"cvss":{"score":5.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An information exposure vulnerability in Datart v1.0.0-rc.3 allows authenticated attackers to access sensitive data via a custom H2 JDBC connection string.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-02-14","github_poc":1,"max_poc_stars":4,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-02-14T02:14:02Z","kind":"github_poc","ref":"https://github.com/xiaoxiaoranxxx/CVE-2025-70829","stars":4,"title":" An information exposure vulnerability in Datart v1.0.0-rc.3 allows authenticated attackers to access sensitive data via a custom H2 JDBC connection string."}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2025-70829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2025-70830"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-70828"},"products":["n/a"],"published":"2026-02-17","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2025-56819","kev_date_added":null,"published":"2025-09-24"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2025-70828","kev_date_added":null,"published":"2026-02-17"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2025-56816","kev_date_added":null,"published":"2025-09-24"},{"cvss_score":7.1,"headline":"Path traversal in n/a","id":"CVE-2025-56815","kev_date_added":null,"published":"2025-09-24"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-17","vendors":["n/a"]},"summary":"Authenticated attackers can access sensitive data in Datart by exploiting a custom H2 JDBC connection string vulnerability.","url":"https://insights.sbomify.com/CVE-2025-70829/"}