{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-34054 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34054 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34054 is a high-severity path traversal vulnerability in microsoft vcpkg, published on 31 Mar 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-2026-34054 and fix it if it is affected.\n\nWhat it is: CVE-2026-34054 is a high-severity path traversal vulnerability in microsoft vcpkg, published on 31 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34054 in the wild and no public exploit code.\n\nAffected product: microsoft vcpkg. 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-34054/ (Markdown: https://insights.sbomify.com/CVE-2026-34054/index.md)","id":"CVE-2026-34054","markdown":"https://insights.sbomify.com/CVE-2026-34054/index.md","name":"CVE-2026-34054","record":{"aliases":["GHSA-p322-v6vw-vrq9"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"vcpkg package manager","requires_auth":"low_privilege","summary":"vcpkg's Windows OpenSSL builds used a hardcoded build-machine path, allowing attackers to execute code via uncontrolled search path elements on customer machines.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"vcpkg is a free and open-source C/C++ package manager. Prior to version 3.6.1#3, vcpkg's Windows builds of OpenSSL set openssldir to a path on the build machine, making that path be attackable later on customer machines. This issue has been patched in version 3.6.1#3.","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":"openssl on Windows built with openssldir set from the build machine (Uncontrolled Search Path Element)","id":"CVE-2026-34054","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OpenEMR has IDOR in Patient Notes Web UI allows unauthorized note access/modification","id":"CVE-2026-34055"},"packages":[],"prev":{"headline":"OpenEMR Missing Authorization in Procedure Order AJAX Deletion Handler","id":"CVE-2026-34053"},"products":["vcpkg"],"published":"2026-03-31","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":"total"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["microsoft"]},"summary":"vcpkg's Windows OpenSSL builds used a hardcoded build-machine path, allowing attackers to execute code via uncontrolled search path elements on customer machines.","url":"https://insights.sbomify.com/CVE-2026-34054/"}