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

CVE-2019-5448 — yarn

HIGH

CVE-2019-5448 is a high-severity (CVSS 8.1) CWE-311 vulnerability in yarn. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for yarn — see the affected versions and patch details below.

Missing Encryption of Sensitive Data in yarn

Also known asGHSA-wqfc-cr59-h64p
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk
0.00%0.39%0.78%1.17%0.1%0.7%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

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.3npm install yarn@1.17.3

Affected Products

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

Yarn before 1.17.3 is vulnerable to Missing Encryption of Sensitive Data…

github.comNVDOct 2019

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.17.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-5448 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.

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 CVE-2019-5448 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2019-5448: yarn — Fixed in 1.17.3