How severe is GHSA-2vrf-hf26-jrp5?

GHSA-2vrf-hf26-jrp5 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2vrf-hf26-jrp5?

GHSA-2vrf-hf26-jrp5 affects the following packages: angular (npm). Ecosystems affected: npm.

How do I fix GHSA-2vrf-hf26-jrp5?

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.

How do I detect GHSA-2vrf-hf26-jrp5 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 GHSA-2vrf-hf26-jrp5 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 GHSA-2vrf-hf26-jrp5?

O3 pinpoints whether GHSA-2vrf-hf26-jrp5 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 GHSA-2vrf-hf26-jrp5 actively exploited in the wild?

Yes. There are 5 known exploit references for GHSA-2vrf-hf26-jrp5, 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 GHSA-2vrf-hf26-jrp5?

GHSA-2vrf-hf26-jrp5 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 GHSA-2vrf-hf26-jrp5 published, and has it been updated?

GHSA-2vrf-hf26-jrp5 was published on March 30, 2023 and was last updated on February 4, 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

Not in CISA KEV

MEDIUM severity

GHSA-2vrf-hf26-jrp5

MEDIUM

GHSA-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. O3 Security confirms whether GHSA-2vrf-hf26-jrp5 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 via the angular.copy() utility

Also known asCVE-2023-26116

Published

Mar 30, 2023

Updated

Feb 4, 2026

Affected

1 pkg

Patched

None yet

Exploits

5 known

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

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

693Kdownloads / week

Description

All versions of the package angular 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

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`angular`	all versions	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.