{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-14728 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14728 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14728 is a medium-severity path traversal vulnerability in Rapid7 Velociraptor, published on 29 Dec 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-14728 and fix it if it is affected.\n\nWhat it is: CVE-2025-14728 is a medium-severity path traversal vulnerability in Rapid7 Velociraptor, published on 29 Dec 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-14728 in the wild and no public exploit code.\n\nAffected product: Rapid7 Velociraptor. 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-14728/ (Markdown: https://insights.sbomify.com/CVE-2025-14728/index.md)","id":"CVE-2025-14728","markdown":"https://insights.sbomify.com/CVE-2025-14728/index.md","name":"CVE-2025-14728","record":{"aliases":["GHSA-fh4j-chp9-mvg5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Rapid7 Velociraptor","requires_auth":"none","summary":"A rogue client can write files outside the datastore directory on Linux servers due to insufficient sanitization of directory names ending with a dot.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"rapid7","cpe":[{"product":"velociraptor","vendor":"rapid7"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Rapid7 Velociraptor versions before 0.75.6 contain a directory traversal issue on Linux servers that allows a rogue client to upload a file which is written outside the datastore directory. Velociraptor is normally only allowed to write in the datastore directory. The issue occurs due to insufficient sanitization of directory names which end with a \".\", only encoding the final \".\" AS \"%2E\".\n\nAlthough files can be written to incorrect locations, the containing directory must end with \"%2E\". This limits the impact of this vulnerability, and prevents it from overwriting critical files.","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":"Rapid7 Velociraptor Directory Traversal Vulnerability","id":"CVE-2025-14728","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":"CTCMS Content Management System Backend App Configuration Ct_App.php save code injection","id":"CVE-2025-14729"},"packages":[],"prev":{"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2025-14727"},"products":["Velociraptor"],"published":"2025-12-29","related":[{"cvss_score":8.8,"headline":"Insufficient permission check in the VQL copy() function","id":"CVE-2023-0242","kev_date_added":null,"published":"2023-01-18"},{"cvss_score":8.6,"headline":"Rapid7 Velociraptor Reflected XSS","id":"CVE-2023-5950","kev_date_added":null,"published":"2023-11-06"},{"cvss_score":8.5,"headline":"Rapid7 Velociraptor Improper Input Validation in Client Message Handler","id":"CVE-2026-5329","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":8,"headline":"Velociraptor Query() Plugin Misapplies Permissions To Orgs","id":"CVE-2026-6290","kev_date_added":null,"published":"2026-04-15"},{"cvss_score":6.1,"headline":"Unsafe HTML Injection in Artifact Collection Report","id":"CVE-2022-35630","kev_date_added":null,"published":"2022-07-29"},{"cvss_score":5.5,"headline":"Velociraptor priviledge escalation via UpdateConfig artifact","id":"CVE-2025-6264","kev_date_added":null,"published":"2025-06-20"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-30","vendors":["Rapid7"]},"summary":"A rogue client can write files outside the datastore directory on Linux servers due to insufficient sanitization of directory names ending with a dot.","url":"https://insights.sbomify.com/CVE-2025-14728/"}