NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Yarn Improper link resolution before file access (Link Following)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 or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for yarn — see the affected versions and patch details below.

Also known asCVE-2019-10773SNYK-JS-YARN-537806,
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.05%0.70%1.36%2.02%0.5%1.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
yarnnpm
12.8Mdownloads / week

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.0npm install yarn@1.22.0

Affected Products

1 product · 1 configurations
Application
yarnyarnpkg
< 1.21.1
range
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.

In Yarn before 1.21.1, the package install functionality can be abused t…

github.comNVDFeb 2020

Report on blog.daniel-ruf.de

blog.daniel-ruf.deNVDFeb 2020

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
Red Hat Quay 3quay3/clair-jwt:v3.2.1-1RHSA-2020:0475

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Yarn Improper link resolution before file access (Link…