How severe is CVE-2022-31129?

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

Which packages are affected by CVE-2022-31129?

CVE-2022-31129 affects the following packages: moment (npm), Moment.js (NuGet). Ecosystems affected: npm, NuGet.

How do I fix CVE-2022-31129?

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

How do I detect CVE-2022-31129 in my npm, NuGet dependencies?

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

How do I mitigate CVE-2022-31129 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-31129 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2022-31129, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2022-31129 has an EPSS (Exploit Prediction Scoring System) score of 5.6%, placing it in the 93th 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-31129?

CVE-2022-31129 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-1333 (CWE-1333). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2022-31129 was published on July 6, 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.NET NuGet

Not in CISA KEV

HIGH severity

CVE-2022-31129 — moment

HIGHFix: moment/moment@9a3b589

CVE-2022-31129 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in moment. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for moment — see the affected versions and patch details below.

Inefficient Regular Expression Complexity in moment

Also known asGHSA-wc69-rhjr-hc9g

Published

Jul 6, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31129.

EPSS Exploitation Probability

via FIRST.org ↗

5.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% 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

2 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.

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

momentnpm

50.2Mdownloads / week

Description

Impact

using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs
noticeable slowdown is observed with inputs above 10k characters
users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks

Patches

The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking.

Workarounds

In general, given the proliferation of ReDoS attacks, it makes sense to limit the length of the user input to something sane, like 200 characters or less. I haven't seen legitimate cases of date-time strings longer than that, so all moment users who do pass a user-originating string to constructor are encouraged to apply such a rudimentary filter, that would help with this but also most future ReDoS vulnerabilities.

References

There is an excellent writeup of the issue here: https://github.com/moment/moment/pull/6015#issuecomment-1152961973=

Details

The issue is rooted in the code that removes legacy comments (stuff inside parenthesis) from strings during rfc2822 parsing. moment("(".repeat(500000)) will take a few minutes to process, which is unacceptable.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`moment`	≥ 2.18.0&&< 2.29.4	2.29.4`npm install moment@2.29.4`
.NETNuGet	`Moment.js`	≥ 2.18.0&&< 2.29.4	2.29.4`dotnet add package Moment.js --version 2.29.4`

Affected Products

3 products · 6 configurations

debian linuxdebian

1 version

10.0

fedorafedoraproject

3 versions

353637

Application

momentmomentjs

≥ 2.18.0 && < 2.29.4

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

moment is a JavaScript date library for parsing, validating, manipulatin…

github.comNVDJul 2022

Report on huntr.dev

huntr.devNVDJul 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moment, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update moment to 2.29.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31129 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 HatImportant

Red Hat Fuse provides the affected software but does not use the functionality and as such its impact has been downgraded to Low. Red Hat Advanced Cluster Management for Kubernetes (RHACM) ships a vulnerable version of the moment library. However, this affected functionality is restricted behind OAuth, reducing the…

Product	Fixed in	Advisory
OpenShift Service Mesh 2.0	`openshift-service-mesh/kiali-rhel8:1.24.16-1`	RHSA-2022:5913
OpenShift Service Mesh 2.0	`servicemesh-prometheus-0:2.14.0-18.el8.1`	RHSA-2022:6272
OpenShift Service Mesh 2.1	`openshift-service-mesh/kiali-rhel8:1.36.12-1`	RHSA-2022:5914
OpenShift Service Mesh 2.1	`servicemesh-prometheus-0:2.23.0-9.el8`	RHSA-2022:6277
Red Hat Fuse 7.11.1	`moment`	RHSA-2022:8652
Red Hat Gluster Storage 3.5 for RHEL 7	`grafana-0:5.2.4-6.el7rhgs`	RHSA-2023:1486
Red Hat OpenShift Data Foundation 4.11 on RHEL8	`odf4/mcg-core-rhel8:v4.11.0-30`	RHSA-2022:6156
Red Hat OpenShift Service Mesh 2.2 for RHEL 8	`openshift-service-mesh/kiali-rhel8:1.48.2-1`	RHSA-2022:5915

Frequently Asked Questions

### Impact * using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs * noticeable slowdown is observed with inputs above 10k characters * users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks ### Patches The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. ### Workarounds In general, given the proliferation of ReDoS attacks, it makes sense to limit the length of the user input

O3 Security · Impact-Aware SCA

Is CVE-2022-31129 in your dependencies?

Find it across npm, NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works