How severe is CVE-2022-37599?

CVE-2022-37599 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-37599?

CVE-2022-37599 affects the following packages: loader-utils (npm), loader-utils (npm), loader-utils (npm). Ecosystems affected: npm.

How do I fix CVE-2022-37599?

Update loader-utils to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37599 is resolved across your whole dependency graph.

How do I detect CVE-2022-37599 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loader-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-37599 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-37599 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-37599 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-37599?

CVE-2022-37599 has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-37599?

CVE-2022-37599 is classified as CWE-1333 (CWE-1333). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-37599 published, and has it been updated?

CVE-2022-37599 was published on October 11, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2022-37599 — loader-utils

HIGHFix: webpack/loader-utils@17cbf8f

CVE-2022-37599 is a high-severity (CVSS 7.5) CWE-1333 vulnerability in loader-utils. A fix is available for loader-utils — see the affected versions and patch details below.

loader-utils is vulnerable to Regular Expression Denial of Service (ReDoS)

Also known asGHSA-hhq3-ff78-jv3g

Published

Oct 11, 2022

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

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

3 pkgs 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.

7Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

loader-utilsnpm

71.1Mdownloads / week

Description

A regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils via the resourcePath variable in interpolateName.js. A badly or maliciously formed string could be used to send crafted requests that cause a system to crash or take a disproportional amount of time to process. This issue has been patched in versions 1.4.2, 2.0.4 and 3.2.1.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`loader-utils`	≥ 1.0.0&&< 1.4.2	1.4.2`npm install loader-utils@1.4.2`
📦npm	`loader-utils`	≥ 2.0.0&&< 2.0.4	2.0.4`npm install loader-utils@2.0.4`
📦npm	`loader-utils`	≥ 3.0.0&&< 3.2.1	3.2.1`npm install loader-utils@3.2.1`

Affected Products

1 product · 3 configurations

Application

loader-utilswebpack.js

≥ 3.0.0 && < 3.2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loader-utils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update loader-utils to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37599 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 HatModerate

In Red Hat OpenShift Logging the openshift-logging/kibana6-rhel8 container and openshift-logging/logging-view-plugin-rhel8 bundles many nodejs packages as a build time dependencies, including loader-utils package. The vulnerable code is not used hence the impact to OpenShift Logging by this vulnerability is Low.

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2022-37599 (CC BY 4.0)

Product	Fixed in	Advisory
RHPAM 7.13.4 async	`loader-utils`	RHSA-2023:4983

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-37599 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works