Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-wqfc-cr59-h64p

HIGH

GHSA-wqfc-cr59-h64p is a high-severity (CVSS 8.1) CWE-311 vulnerability in yarn. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-wqfc-cr59-h64p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Missing Encryption of Sensitive Data in yarn

Also known asCVE-2019-5448
Published
Jul 31, 2019
Updated
Jun 17, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

yarnnpm
10.4Mdownloads / week

Description

Yarn before 1.17.3 is vulnerable to Missing Encryption of Sensitive Data due to HTTP URLs in lockfile causing unencrypted authentication data to be sent over the network.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmyarnall versions1.17.3
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yarn. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update yarn to 1.17.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wqfc-cr59-h64p is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-wqfc-cr59-h64p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wqfc-cr59-h64p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Yarn before 1.17.3 is vulnerable to Missing Encryption of Sensitive Data due to HTTP URLs in lockfile causing unencrypted authentication data to be sent over the network.
O3 Security · Impact-Aware SCA

Is GHSA-wqfc-cr59-h64p in your dependencies?

O3 detects GHSA-wqfc-cr59-h64p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.