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

GHSA-5xf4-f2fq-f69j

HIGHFix: yarnpkg/yarn#7755

GHSA-5xf4-f2fq-f69j is a high-severity (CVSS 7.8) CWE-59 vulnerability in yarn. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-5xf4-f2fq-f69j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Yarn Improper link resolution before file access (Link Following)

Also known asCVE-2019-10773
Published
Feb 14, 2020
Updated
Jun 17, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known

Real-World Exposure

1 pkg affected
📦yarn

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

In Yarn before 1.21.1, the package install functionality can be abused to generate arbitrary symlinks on the host filesystem by using specially crafted "bin" keys. Existing files could be overwritten depending on the current user permission set.

Affected Packages

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

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.22.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5xf4-f2fq-f69j 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-5xf4-f2fq-f69j 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-5xf4-f2fq-f69j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Yarn before 1.21.1, the package install functionality can be abused to generate arbitrary symlinks on the host filesystem by using specially crafted "bin" keys. Existing files could be overwritten depending on the current user permission set.
O3 Security · Impact-Aware SCA

Is GHSA-5xf4-f2fq-f69j in your dependencies?

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