LiveActive security incident?Get immediate response
CVE Record

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

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 .

HighCVSS 7.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-11998 is a browser-side XSS flaw in AngularJS. A vulnerable application can incorrectly trust a resource URL, allowing unsafe JavaScript to run in a victim's session. AngularJS was already end-of-life when disclosed, so the upstream project will not issue a fix.

Executive priority

High priority for internet-facing or user-facing legacy AngularJS apps. The main business risk is account or data compromise through browser-session JavaScript execution, with no upstream patch path because the framework is end-of-life.

Technical view

AngularJS SCE resource URL policy matching can partially match certain regular expressions instead of enforcing intended full-URL matches. That can bypass SCE controls for resource URLs used by scripts, iframes, templates, or similar contexts. Affected versions are AngularJS >=1.2.0-rc.3.

Likely exposure

Exposure is most likely in legacy AngularJS applications using SCE resource URL allowlists and dynamic resource URLs influenced by user, tenant, CMS, routing, or integration data.

Exploitation context

The source bundle includes public technical and exploit-tagged references, but KEV is false and no provided source states active exploitation. CVSS indicates network attack vector, low complexity, no privileges required, and required user interaction.

Researcher notes

Focus review on SCE delegate resource URL policy configuration and regex matcher assumptions. Evidence supports the class, affected range, and public technical references; it does not support claims of active exploitation or an official upstream fix.

Mitigation direction

  • Inventory AngularJS applications and identify versions >=1.2.0-rc.3.
  • Review vendor and extended-support guidance; upstream AngularJS will not patch.
  • Reduce or remove dynamic resource URL construction in AngularJS views and routes.
  • Treat untrusted input in resource URL contexts as unsafe until reviewed.
  • Prioritize migration away from end-of-life AngularJS where feasible.

Validation and detection

  • Search application dependencies for the angular package and affected version ranges.
  • Review SCE resource URL whitelist and blacklist regular expressions.
  • Identify whether user-controlled data can influence script, iframe, route template, or resource URLs.
  • Confirm compensating changes against vendor guidance without relying on upstream AngularJS updates.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-791: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-11998 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L2.84.7HeroDevs
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L2.84.7redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2026-11998Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPangularjs: AngularJS: Arbitrary JavaScript execution due to Strict Contextual Escaping (SCE) bypass
other:Red Hat severity ratingcvssV3_1
  • 2026-06-24T22:02:28.751Z: Reported to Red Hat.
  • 2026-06-24T20:29:37.188Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAngularJSangular, >=1.2.0-rc.3unaffected
Weakness

CWE details

CWE-79CWE-791

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-791 · source CWE mapping

Incomplete Filtering of Special Elements

Incomplete Filtering of Special Elements represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs