CVE-2022-37598: Prototype pollution vulnerability in function DEFNODE in ast.js in mishoo UglifyJS 3.13.2 via the name variabl

Q: How do I fix CVE-2022-37598?

uglifyjs: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2022-37598 being exploited?

CVE-2022-37598 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-37598 affect?

CVE-2022-37598 affects uglifyjs. Severity is critical (CVSS 9.8). Prototype pollution vulnerability in function DEFNODE in ast.js in mishoo UglifyJS 3.13.2 via the name variable in ast.js. NOTE: the vendor considers this an invalid report.

Q: How urgent is CVE-2022-37598?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2022-37598 is a critical-severity flaw (CVSS 9.8) affecting uglifyjs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Prototype pollution vulnerability in function DEFNODE in ast.js in mishoo UglifyJS 3.13.2 via the name variable in ast.js. NOTE: the vendor considers this an invalid report.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.9% (top 20%)
CISA exploited list	No
Weakness	CWE-1321
Published	2022-10-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: uglifyjs project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-10-20 11:15 UTCPublished CVE record published
2026-06-17 04:55 UTCUpdated Record last modified

uglifyjs project uglifyjs DOWNGRADE

Affected: 3.13.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.13.2

1. Check installed version

npm ls uglifyjs

2. No fixed release: DOWNGRADE to a release before 3.13.2

npm view uglifyjs versions npm install uglifyjs@"<3.13.2"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-37598?

uglifyjs: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-37598 being exploited?

CVE-2022-37598 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-37598 affect?

CVE-2022-37598 affects uglifyjs. Severity is critical (CVSS 9.8). Prototype pollution vulnerability in function DEFNODE in ast.js in mishoo UglifyJS 3.13.2 via the name variable in ast.js. NOTE: the vendor considers this an invalid report.

How urgent is CVE-2022-37598?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs