# CVE-2026-11998: AngularJS XSS via SCE resource URL sanitization bypass

> Attacker can execute arbitrary JavaScript in victim's browser by bypassing AngularJS SCE resource URL sanitization policies.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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:** 24 Jun 2026
- **Updated:** 5 Aug 2026
- **Also known as:** CLSA-2026-1784769553, CLSA-2026-1784769554, CLSA-2026-1784769558, CLSA-2026-1784769564, CLSA-2026-1784769597, DEBIAN-CVE-2026-11998, GHSA-7x27-g8rg-x87w, ROOT-APP-NPM-CVE-2026-11998, UBUNTU-CVE-2026-11998

## What is CVE-2026-11998?

CVE-2026-11998 is a high-severity cross-site scripting vulnerability in Google AngularJS, published on 24 Jun 2026. 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 flaw in AngularJS' Strict Contextual Escaping (SCE) logic allows bypassing certain SCE policies for resource URLs and can lead to arbitrary JavaScript execution within the context of the victim's browser session.

SCE's purpose is to ensure that only trusted or safe values are used in certain security-sensitive contexts, such as resource URLs, including URLs that define executable JavaScript scripts, '<iframe>' documents, route templates, etc. A flaw in the logic that tries to match entire URLs against regular expression matchers can result in partial matches for certain types of regular expressions, effectively bypassing the policies and allowing the use of unsafe values as resource URLs.

This issue affects AngularJS versions greater than or equal to 1.2.0-rc.3.

Note:
The AngularJS project was already End-of-Life when this CVE was published and will not receive any updates to address this issue. For more information see the  End-of-Life announcement https://docs.angularjs.org/misc/version-support-status .

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-791 (Incomplete Filtering of Special Elements)

## Which versions are affected by CVE-2026-11998?

2 open source packages ship an affected version, including angular.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `angular` | npm | From 1.2.0-rc.3 to 1.8.3 | None |
| `angular` | npm | From 1.2.0-rc.3 to 1.8.3 | None |

## How do I fix CVE-2026-11998?

Product is end of life, replace it.

## Is CVE-2026-11998 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11998 and fix it if it is affected.

What it is: CVE-2026-11998 is a high-severity cross-site scripting vulnerability in Google AngularJS, published on 24 Jun 2026. 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-2026-11998 exists.

Affected packages and fixed versions:
- angular (npm): affected from 1.2.0-rc.3 up to 1.8.3; no fix listed
- angular (npm): affected from 1.2.0-rc.3 up to 1.8.3; no fix listed

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-2026-11998/ (Markdown: https://insights.sbomify.com/CVE-2026-11998/index.md)
```

## Sources

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

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