CVE-2026-111753angular sensitive data in a response
CVE-2026-111753 is a sensitive data in a response in angular, rated medium (5.9 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
A response carries data the caller should not receive.
How it is reached
An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker learn data or internals that help a follow-up attack.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade angular to a fixed version for your release line (20.3.34, 21.0.3).
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
- APIs that over-share. The flaw sits between internal data and whoever can read the response or log.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.
Questions to answer about your own systems
- Where does angular run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Patches and commits
Releases
Issue reports
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.