MediumCVE-2026-111753

    Angular: Insertion of Sensitive Information Into Sent Data (CVE-2026-111753)

    Published Last modified Sources: BSI, OSV, Hersteller, CVE.org

    Share

    What is affected, what to do

    Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.34 and 21.0.3, the @angular/common HttpClient function xsrfInterceptorFn uses a regular expression that does not normalize request URLs in the same way as the browser's WHATWG URL parser.

    Update Angular to version 21.0.3, @angular/common to version 20.3.34.

    Affected
    • Angular gte 20.0.0, < 20.3.34..*
    • Angular lte *..19.2.25

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    5.9

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    5.9

    CVSS v4

    Severity Medium on the scale from 0 to 10.

    Source: BSI, OSV, Hersteller, CVE.org

    0.5 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 45.4

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    76.02 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    5.9 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    5.9
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.5 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    45.4
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-201, CWE-359

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.34 and 21.0.3, the @angular/common HttpClient function xsrfInterceptorFn uses a regular expression that does not normalize request URLs in the same way as the browser's WHATWG URL parser. With XSRF protection enabled, a mutating HTTP request to an attacker-controlled URL containing backslashes, stripped control characters or spaces, or removable ASCII whitespace can be misclassified as relative and same-origin, causing the interceptor to attach the X-XSRF-TOKEN header before the browser dispatches the request to a cross-origin host. With permissive CORS handling for the custom header, the attacker can obtain the victim's XSRF token and use it to perform cross-site request forgery against the victim session. This issue is fixed in versions 20.3.34 and 21.0.3.

    Source: BSI CSAF, BSI WID Portal, OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    angularangular
    • ≤ 19.2.25
    • ≥ 20.0.0, < 20.3.34
    • —
    • —
    Open SourceAngular
    • < 21.0.3
    • < 20.3.34
    • 21.0.3
    • 20.3.34
    npm@angular/common
    • 20.0.0
    • >= 21.0.0, < 21.0.3
    • —
    • 21.0.0
    • <= 19.2.25
    • >= 20.0.0, < 20.3.34
    • 20.3.34
    • 21.0.3
    • —
    • 21.0.3
    • —
    • 20.3.34

    Vendors and products

    Weakness classes (CWE)

    • CWE-201Insertion of Sensitive Information Into Sent Data

      Base

      The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

      Entry at MITRE CWE-201

    • CWE-359Exposure of Private Personal Information to an Unauthorized Actor

      Base

      The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.

      Entry at MITRE CWE-359

    References & sources

    • github.comangular/angular/security/advisories/GHSA-jfgx-762w-99vrweb, x_refsource_CONFIRM
    • github.comangular/angular/pull/65683web, x_refsource_MISC
    • github.comangular/angular/pull/71295web, x_refsource_MISC
    • github.comangular/angular/commit/0659d11c854c9c6b886a2e925afef98d70bb005fweb
    • github.comangular/angular/commit/20474d3f0fd7c64071add6e84acf720627e5c19bweb, x_refsource_MISC
    • github.comangular/angular/commit/933ce817d53e25926844fa56af8230816763d08eweb, x_refsource_MISC
    • github.comangular/angularpackage
    • github.comangular/angular/issues/71294x_refsource_MISC
    • github.comangular/angular/releases/tag/21.0.3x_refsource_MISC
    • github.comangular/angular/releases/tag/v20.3.34x_refsource_MISC

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedGitHub

      CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

      Weakness type: CWE-201, CWE-359

      Description added or changed

      Show 13 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.34 and 21.0.3, the @angular/common HttpClient function xsrfInterceptorFn uses a regular expression that does not normalize request URLs in the same way as the browser's WHATWG URL parser. With XSRF protection enabled, a mutating HTTP request to an attacker-controlled URL containing backslashes, stripped control characters or spaces, or removable ASCII whitespace can be misclassified as relative and same-origin, causing the interceptor to attach the X-XSRF-TOKEN header before the browser dispatches the request to a cross-origin host. With permissive CORS handling for the custom header, the attacker can obtain the victim's XSRF token and use it to perform cross-site request forgery against the victim session. This issue is fixed in versions 20.3.34 and 21.0.3.
      CVSSadded
      —
      AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      Weakness type (CWE)added
      —
      CWE-201
      Weakness type (CWE)added
      —
      CWE-359
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/111xxx/CVE-2026-111753.json">CVE-2026-111753</a>
      Referenceadded
      —
      https://github.com/angular/angular/commit/20474d3f0fd7c64071add6e84acf720627e5c19b
      Referenceadded
      —
      https://github.com/angular/angular/commit/933ce817d53e25926844fa56af8230816763d08e
      Referenceadded
      —
      https://github.com/angular/angular/issues/71294
      Referenceadded
      —
      https://github.com/angular/angular/pull/65683
      Referenceadded
      —
      https://github.com/angular/angular/pull/71295
      Referenceadded
      —
      https://github.com/angular/angular/releases/tag/21.0.3
      Referenceadded
      —
      https://github.com/angular/angular/releases/tag/v20.3.34
      Referenceadded
      —
      https://github.com/angular/angular/security/advisories/GHSA-jfgx-762w-99vr

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-111753
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-111753"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-111753.svg?lang=en" alt="CVE-2026-111753 – NEOSEC Intel" height="20"></a>