How severe is CVE-2022-25844?

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

Which packages are affected by CVE-2022-25844?

CVE-2022-25844 affects the following packages: angular (npm). Ecosystems affected: npm.

How do I fix CVE-2022-25844?

No patched version of angular has shipped for CVE-2022-25844 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for angular. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

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.

How does O3 Security protect against CVE-2022-25844?

O3 pinpoints whether CVE-2022-25844 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Yes. There are 5 known exploit references for CVE-2022-25844, including 5 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 type of vulnerability is CVE-2022-25844?

CVE-2022-25844 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-25844 published, and has it been updated?

CVE-2022-25844 was published on May 1, 2022 and was last updated on April 16, 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

CVE-2022-25844

HIGH

CVE-2022-25844 is a high-severity (CVSS 7.5) CWE-1333 vulnerability in angular. 5 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2022-25844 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

angular vulnerable to regular expression denial of service (ReDoS)

Also known asGHSA-m2h2-264f-f486

Published

May 1, 2022

Updated

Apr 16, 2026

Affected

1 pkg

Patched

None yet

Exploits

5 known

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

angularnpm

691Kdownloads / week

Description

The package angular after 1.7.0 are vulnerable to Regular Expression Denial of Service (ReDoS) by providing a custom locale rule that makes it possible to assign the parameter in posPre: ' '.repeat() of NUMBER_FORMATS.PATTERNS[1].posPre with a very high value. Note: 1) This package has been deprecated and is no longer maintained. 2) The vulnerable versions are 1.7.0 and higher.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`angular`	≥ 1.7.0	No fix

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.