GHSA-2vrf-hf26-jrp5 — angular
MEDIUMGHSA-2vrf-hf26-jrp5 is a medium-severity (CVSS 5.3) CWE-1333 vulnerability in angular. 5 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.
angular vulnerable to regular expression denial of service via the angular.copy() utility
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 GHSA-2vrf-hf26-jrp5.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-2vrf-hf26-jrp5 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
angularReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Versions of the package angular from 1.2.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the angular.copy() utility function due to the usage of an insecure regular expression. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | angular | all versions | No fix |
Affected Products
angularjsangularjsfedorafedoraprojectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Versions of the package angular from 1.2.21 are vulnerable to Regular Ex…
Versions of the package angular from 1.2.21 are vulnerable to Regular Ex…
Versions of the package angular from 1.2.21 are vulnerable to Regular Ex…
Versions of the package angular from 1.2.21 are vulnerable to Regular Ex…
Versions of the package angular from 1.2.21 are vulnerable to Regular Ex…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for angular, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of angular has shipped for GHSA-2vrf-hf26-jrp5 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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.
Frequently Asked Questions
Is GHSA-2vrf-hf26-jrp5 in your dependencies?
Find it across npm, including transitive dependencies.