Skip to main content
VulnerabilityPublished Updated

CVE-2023-26116: angular · Regular Expression Denial of Service

Affects angularSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Mar 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npmangularpkg:npm/angularOther threatsAffected
  • =1.2.21
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2023-26116, European organizations should: 1) Upgrade Angular from version 1.2.21 to the latest supported version where the vulnerability is patched or no longer present. If upgrading is not immediately feasible, consider applying any available patches or backported fixes. 2) Implement strict input validation and size limits on data passed to angular.copy() or related functions to prevent large, malicious payloads from triggering the regex. 3) Employ Web Application Firewalls (WAFs) with rules designed to detect and block suspicious payloads that could exploit regex vulnerabilities. 4) Monitor application performance metrics and logs for unusual CPU spikes or slowdowns indicative of ReDoS attempts. 5) Conduct code reviews and security testing focusing on regular expression usage in legacy codebases. 6) Educate developers about the risks of inefficient regular expressions and encourage secure coding practices. 7) Isolate legacy applications behind network segmentation to reduce exposure. These steps collectively reduce the risk of exploitation and improve detection and response capabilities.

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.

References

Community reviews

Loading reviews…