# CVE-2025-4690: AngularJS 'linky' filter ReDoS

> Attackers can cause denial of service in applications using AngularJS via ReDoS in the linky filter; the library is end-of-life with no fix.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Aug 2025
- **Updated:** 19 Aug 2025
- **Also known as:** CLSA-2026-1785554487, CLSA-2026-1785554488, DEBIAN-CVE-2025-4690, GHSA-hfff-63hg-f47j, UBUNTU-CVE-2025-4690

## What is CVE-2025-4690?

CVE-2025-4690 is a medium-severity denial of service vulnerability in Google AngularJS, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A regular expression used by AngularJS'  linky https://docs.angularjs.org/api/ngSanitize/filter/linky  filter to detect URLs in input text is vulnerable to super-linear runtime due to backtracking. With a large carefully-crafted input, this can cause a 

 Regular expression Denial of Service (ReDoS) https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS  attack on the application.

This issue affects all versions of AngularJS.

Note:
The AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see  here https://docs.angularjs.org/misc/version-support-status .

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2025-4690?


## How do I fix CVE-2025-4690?

Product is end of life, replace it.

## Is CVE-2025-4690 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4690 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4690 and fix it if it is affected.

What it is: CVE-2025-4690 is a medium-severity denial of service vulnerability in Google AngularJS, published on 19 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4690 exists.

Affected product: Google AngularJS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-4690/ (Markdown: https://insights.sbomify.com/CVE-2025-4690/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4690
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4690
- OSV: https://osv.dev/vulnerability/CVE-2025-4690

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-4690/
Summaries are generated and may contain mistakes; the official description above is the record.