CVE-2026-11998
HIGHDescription
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 .
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
Exploit Intelligence
Moderate risk: more likely to be exploited than 41% of all known CVEs.
References
Related Vulnerabilities
Other CWE-791 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-21668 | High | 8.0 | 3.9% | - | Fix |
| CVE-2022-2132 | High | 8.6 | 2.2% | - | Fix |
| CVE-2026-47323 | Critical | 9.8 | 1.5% | - | Fix |
| CVE-2026-29186 | High | 7.7 | 0.8% | - | Fix |
| CVE-2024-47590 | High | 8.8 | 0.8% | - | - |
| CVE-2026-2969 | Medium | 4.7 | 0.7% | - | - |
Common questions
How do I fix CVE-2026-11998?
No published fix for CVE-2026-11998 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-11998 being actively exploited?
Not that we know of. CVE-2026-11998 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.50% is the estimated probability that it will be exploited in the next 30 days. That is higher than 41% of all scored CVEs.
How severe is CVE-2026-11998?
CVE-2026-11998 has a CVSS v3 base score of 7.6, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-11998
Markdown
[](https://tridentstack.com/cve/CVE-2026-11998)HTML
<a href="https://tridentstack.com/cve/CVE-2026-11998"><img src="https://tridentstack.com/cve/badge/CVE-2026-11998.svg" alt="CVE-2026-11998"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-05.