Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

DLL Injection in kerberosGHSA-m2mx-rfpw-jghv

HIGH

GHSA-m2mx-rfpw-jghv is a high-severity (CVSS 7.8) CWE-427 vulnerability in kerberos. 2 public exploit references exist, so weaponization risk is real. A fix is available for kerberos — see the affected versions and patch details below.

Also known asCVE-2020-13110
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 11, 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 CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.00%0.41%0.82%1.24%0.1%0.7%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-m2mx-rfpw-jghv by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

172other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
kerberosnpm
427Kdownloads / week

Description

Version of kerberos prior to 1.0.0 are vulnerable to DLL Injection. The package loads DLLs without specifying a full path. This may allow attackers to create a file with the same name in a folder that precedes the intended file in the DLL path search. Doing so would allow attackers to execute arbitrary code in the machine.

Recommendation

Upgrade to version 1.0.0 or later.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmkerberosall versions1.0.0npm install kerberos@1.0.0

Affected Products

1 product · 1 configurations
Application
kerberoskerberos_project
< 1.0.0
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.

The kerberos package before 1.0.0 for Node.js allows arbitrary code exec…

medium.comNVDMay 2020

The kerberos package before 1.0.0 for Node.js allows arbitrary code exec…

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

  2. Fix

    Update kerberos to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2mx-rfpw-jghv 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

Version of `kerberos` prior to 1.0.0 are vulnerable to DLL Injection. The package loads DLLs without specifying a full path. This may allow attackers to create a file with the same name in a folder that precedes the intended file in the DLL path search. Doing so would allow attackers to execute arbitrary code in the machine. ## Recommendation Upgrade to version 1.0.0 or later.
O3 Security · Impact-Aware SCA

Is GHSA-m2mx-rfpw-jghv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
DLL Injection in kerberos (High 7.8)