CVE-2022-31129
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 5.55 % · percentile 93.00 % · scored 18 Nov 2026.
Saved 18 Nov 2026 15:46:44 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a 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. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.
Read the publisher's advisorymoment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a 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. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.
Read the publisher's advisorymoment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a 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. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.
Read the publisher's advisory### 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.
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 5.55 % · percentile 93.00 % · scored 18 Nov 2026.
Saved 18 Nov 2026 15:46:44 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2022-31129 · 18 Nov 2026 15:46:44 UTC
CVE-2022-31129 · 17 Nov 2026 15:26:11 UTC
CVE-2022-31129 · 17 Nov 2026 02:39:16 UTC
CVE-2022-31129 · 15 Nov 2026 14:45:34 UTC
CVE-2022-31129 · 14 Nov 2026 16:37:01 UTC
CVE-2022-31129 · 13 Nov 2026 19:59:34 UTC
CVE-2022-31129 · 12 Nov 2026 18:18:51 UTC
CVE-2022-31129 · 10 Nov 2026 20:24:10 UTC
CVE-2022-31129 · 09 Nov 2026 21:04:24 UTC
CVE-2022-31129 · 08 Nov 2026 15:12:21 UTC
CVE-2022-31129 · 07 Nov 2026 16:07:52 UTC
CVE-2022-31129 · 06 Nov 2026 19:10:17 UTC
CVE-2022-31129 · 05 Nov 2026 22:49:22 UTC
CVE-2022-31129 · 05 Nov 2026 02:54:06 UTC
CVE-2022-31129 · 03 Nov 2026 16:59:18 UTC
CVE-2022-31129 · 02 Nov 2026 23:59:04 UTC
CVE-2022-31129 · 01 Nov 2026 23:58:58 UTC
CVE-2022-31129 · 01 Nov 2026 03:04:52 UTC
CVE-2022-31129 · 31 Oct 2026 01:52:30 UTC
CVE-2022-31129 · 29 Oct 2026 18:29:26 UTC
CVE-2022-31129 · 28 Oct 2026 19:55:37 UTC
CVE-2022-31129 · 27 Oct 2026 15:46:19 UTC
CVE-2022-31129 · 27 Oct 2026 00:23:05 UTC
CVE-2022-31129 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
euvd · EUVD-2022-6433 · Published
nvd · CVE-2022-31129 · Published
osv · GHSA-wc69-rhjr-hc9g · Published
cve-program · CVE-2022-31129 · Published