CVE-2026-11998
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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 .
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAngularJS SCE (Strict Contextual Escaping) has a regex matching flaw that allows partial matches against policy regexes, enabling unsafe values (like javascript: URLs) to be used in security-sensitive contexts such as resource URLs, iframes, and route templates, leading to arbitrary JavaScript execution in victim browsers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if AngularJS is in useSearch codebase and build artifacts for angular.js, angular.min.js, or angular npm package referencesAffected if AngularJS library files or package references are found in the environment
-
Determine AngularJS versionCheck the angular.version object in browser console (angular.version.full) or inspect the angular.js file header for version commentAffected if Running any AngularJS version with Strict Contextual Escaping (SCE) enabled (SCE was introduced in AngularJS 1.0.0 and is on by default until 1.2.x where it requires explicit opt-in, then opt-out in later versions)
-
Check if SCE is enabledLook for $sceProvider.enabled(true) or $provide.decorator('$sce', ...) configurations in app code, or check if $sce service is being used for resource URLtrusting (e.g., $sce.trustAsResourceUrl())Affected if SCE is explicitly enabled or remains in default enabled state for the version in use
-
Identify resource URL configurationsSearch codebase for ng-src (for iframes), script tag with ng-include or templateUrl directives, $http or $resource calls loading templates from URLs, and $sce.trustAsResourceUrl() usageAffected if Application loads external templates, scripts, or iframes from user-controlled or partially-matched URLs via SCE-trusted methods
Affected if AngularJS is running with SCE enabled and the application uses resource URLs (script src, iframe src, route templates) that could be matched by the flawed regex allowing partial URL bypass.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedSince AngularJS is End-of-Life and will not receive patches, migrate to modern Angular (2+) or implement additional output encoding/validation layers on the server and client side to sanitize URLs before they reach AngularJS templates.
- 1. Review the SCE bypass vulnerability description: AngularJS 1.x is End-of-Life and will not receive official security patches for CVE-2026-11998.
- 2. Audit existing codebase for all uses of $sce, $sceDelegateProvider, ng-src, ng-include, and any resource URL bindings that may be user-influenced.
- 3. Implement additional input validation and sanitization at the application layer before binding any URLs to SCE-protected contexts.
- 4. Configure Content Security Policy (CSP) headers to restrict script execution and iframe sources as a defense-in-depth measure.
- 5. Consider migrating from AngularJS (1.x) to a supported framework (Angular 2+ or modern alternatives) as the long-term solution since AngularJS will not be patched.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation16.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11998 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11998 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data