{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56816 exists.","fix":"No fix has been published for CVE-2025-56816 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56816 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-56816 and fix it if it is affected.\n\nWhat it is: CVE-2025-56816 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56816 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-56816/ (Markdown: https://insights.sbomify.com/CVE-2025-56816/index.md)","id":"CVE-2025-56816","markdown":"https://insights.sbomify.com/CVE-2025-56816/index.md","name":"CVE-2025-56816","record":{"aliases":["GHSA-pqpp-98pw-x43g"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Datart BI platform","requires_auth":"none","summary":"Attackers can achieve remote code execution by uploading malicious YAML files that trigger unsafe deserialization in Datart.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"datart","vendor":"running-elephant"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Datart 1.0.0-rc.3 is vulnerable to Directory Traversal. The configuration file handling of the application allows attackers to upload arbitrary YAML files to the config/jdbc-driver-ext.yml path. The application parses this file using SnakeYAML's unsafe load() or loadAs() method without input sanitization. This allows deserialization of attacker-controlled YAML content, leading to arbitrary class instantiation. Under certain conditions, this can be exploited to achieve remote code execution (RCE).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Deserialization in n/a","id":"CVE-2025-56816","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2025-56819"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-56815"},"products":["n/a"],"published":"2025-09-24","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":7.1,"headline":"Path traversal in n/a","id":"CVE-2025-56815","kev_date_added":null,"published":"2025-09-24"},{"cvss_score":5.7,"headline":"Information disclosure in n/a","id":"CVE-2025-70829","kev_date_added":null,"published":"2026-02-17"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-09-24","vendors":["n/a"]},"summary":"Attackers can achieve remote code execution by uploading malicious YAML files that trigger unsafe deserialization in Datart.","url":"https://insights.sbomify.com/CVE-2025-56816/"}