CVE-2023-26118: Regular Expression Denial of Service in angular

angular Updated 02 Oct 2025

Summary

30/03/2023
No i
Moderate
5.3

CVE-2023-26118: angular vulnerable to regular expression denial of service via the element. Affects angular versions < 1.8.3. No fix is published. How to fix ↓

Also tracked for

The same CVE-2023-26118 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Angular is an open-source JavaScript framework developed by Google. It is widely used for building web applications and provides a comprehensive set of features for creating dynamic and responsive user interfaces. However, all versions of the package angular are vulnerable to Regular Expression Denial of Service (ReDoS) via the <input type="url"> element. This vulnerability arises due to the usage of an insecure regular expression in the input[url] functionality. An attacker can exploit this vulnerability by providing a large carefully-crafted input, leading to catastrophic backtracking.

Vulnerability Detail

The vulnerability in angular allows an attacker to perform a Regular Expression Denial of Service attack. By providing a specially crafted input, such as a long URL, an attacker can cause the regular expression used in the <input type="url"> element to exhibit catastrophic backtracking. This can result in a significant slowdown or even a denial of service condition. The impact of this vulnerability can be severe, as it can affect the availability and performance of the application.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If updating the angular package is not immediately feasible, a temporary workaround can be implemented. One possible workaround is to validate the input manually on the server-side, using a more efficient and secure regular expression or alternative validation methods. This can help mitigate the risk of a ReDoS attack until the package can be updated.

Conclusion

In conclusion, the angular package is vulnerable to Regular Expression Denial of Service (ReDoS) via the <input type="url"> element. This vulnerability can be exploited by providing a large carefully-crafted input, leading to catastrophic backtracking. It is crucial to update the angular package to a patched version or implement a temporary workaround to mitigate the risk. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for angular →

Share this vulnerability

FAQ

Angular is an open-source JavaScript framework developed by Google. It is used for building web applications and provides a comprehensive set of features for creating dynamic and responsive user interfaces.

Regular Expression Denial of Service (ReDoS) is a type of vulnerability that arises when a regular expression is used in a way that allows an attacker to craft a malicious input that causes the regular expression engine to exhibit catastrophic backtracking. This can lead to a significant slowdown or even a denial of service condition.

An attacker can exploit this vulnerability in angular by providing a large carefully-crafted input, such as a long URL, which triggers the insecure regular expression to exhibit catastrophic backtracking. This can result in a significant slowdown or denial of service.

The impact of this vulnerability can be severe, as it can affect the availability and performance of the application. An attacker can potentially cause a denial of service condition by exploiting this vulnerability.

To fix this vulnerability, it is recommended to update the angular package to a version that includes a patch for this issue. The maintainers of angular have released a fix in version 1.8.4 and later.

Related vulnerabilities

Recent vulnerabilities recorded for angular.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback