{"answers":{"affected":"It affects 3 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69430 exists.","fix":"No fix has been published for CVE-2025-69430 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69430 is a medium-severity path traversal vulnerability in n/a, published on 3 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-69430 and fix it if it is affected.\n\nWhat it is: CVE-2025-69430 is a medium-severity path traversal vulnerability in n/a, published on 3 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-69430 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-69430/ (Markdown: https://insights.sbomify.com/CVE-2025-69430/index.md)","id":"CVE-2025-69430","markdown":"https://insights.sbomify.com/CVE-2025-69430/index.md","name":"CVE-2025-69430","record":{"aliases":["GHSA-2cqf-mg5g-39xv"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yottamaster NAS","requires_auth":"none","summary":"Attackers can read or modify internal NAS files by inserting a USB drive with a crafted symbolic link, affecting Yottamaster NAS devices.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dm200_firmware","vendor":"yottamaster"},{"product":"dm2_firmware","vendor":"yottamaster"},{"product":"dm3_firmware","vendor":"yottamaster"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"An Incorrect Symlink Follow vulnerability exists in multiple Yottamaster NAS devices, including DM2 (version equal to or prior to V1.9.12), DM3 (version equal to or prior to V1.9.12), and DM200 (version equal to or prior to V1.2.23) that could be exploited by attackers to leak or tamper with the internal file system. Attackers can format a USB drive to ext4, create a symbolic link to its root directory, insert the drive into the NAS device's slot, then access the USB drive's symlink directory mounted on the NAS to obtain all files within the NAS system and tamper with those files.","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":"Path traversal in n/a","id":"CVE-2025-69430","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2025-69431"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-69429"},"products":["n/a"],"published":"2026-02-03","related":[{"cvss_score":5.3,"headline":"Yottamaster DM2/DM3/DM200 File Upload path traversal","id":"CVE-2025-14224","kev_date_added":null,"published":"2025-12-08"}],"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":"2026-02-06","vendors":["n/a"]},"summary":"Attackers can read or modify internal NAS files by inserting a USB drive with a crafted symbolic link, affecting Yottamaster NAS devices.","url":"https://insights.sbomify.com/CVE-2025-69430/"}