CVE-2026-34054 openssl on Windows built with openssldir set from the build machine (Uncontrolled Search Path Element)

High 7.8 Published Updated

vcpkg's Windows OpenSSL builds used a hardcoded build-machine path, allowing attackers to execute code via uncontrolled search path elements on customer machines.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-34054?

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.

Official 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.

Weakness: CWE-427

Which versions are affected by CVE-2026-34054?

How do I fix CVE-2026-34054?

No fix has been published for CVE-2026-34054 yet. Limit exposure of the affected software until one is available.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-34054 being exploited?

There is no known exploitation of CVE-2026-34054 in the wild and no public exploit code.

Sources

Also known as GHSA-p322-v6vw-vrq9.

Is CVE-2026-34054 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free