NVD / CVE Program· CNA GitHub_M

CVE-2026-88059: Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`

Noroxi assessment

Priority: Monitor (action score 23/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: @angular/common (npm) 20.3.28, 21.2.20, 22.1.1.

Low priority for now. Upgrade to @angular/common (npm) 20.3.28, 21.2.20, 22.1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.28, 21.2.20, and 22.1.1, Angular's @angular/common HttpTransferCache can cache an authenticated response when Server-Side Rendering (SSR) and hydration use a hierarchical HttpClient configured with withRequestsMadeViaParent. The child TransferCache evaluates an initially anonymous request before delegation, then a parent withInterceptors chain adds an Authorization header, cookie, or API token; although the parent cache skips the authenticated request, the child still stores the private response in TransferState serialized as JSON in the ng-state script. Exploitation requires provideClientHydration, child provideHttpClient delegation through withRequestsMadeViaParent, parent-level credential injection, and an SSR HTML response shared across users by a CDN, reverse proxy, or application cache. A later unauthenticated or unauthorized visitor can receive the cached HTML containing the earlier authenticated user's sensitive response data. Applications can mitigate by attaching credentials at the child, filtering sensitive endpoints with withHttpTransferCacheOptions, disabling transfer caching for sensitive routes, or marking personalized HTML private or no-store. This issue is fixed in versions 20.3.28, 21.2.20, and 22.1.1.

MediumCVSS 5.8 · v3.1—No exploit Fix available

Published: Sep 10, 2026
Updated: Sep 29, 2026
EPSS: 0.3% · 27th percentile
CWE: CWE-200

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 23 / 40 · 5.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.8
CNA · GitHub_M: 4.0; 1.8 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
angular	angular	cpe:2.3:a:angular:angular

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

angular angular19.0.0 and later · up to 19.2.25 inclusive
angular angular20.0.0 and later · before 20.3.28
angular angular21.0.0 and later · before 21.2.20
angular angular22.0.0 and later · before 22.1.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

angular angular
- <= 19.2.25, >= 20.0.0, < 20.3.28, >= 21.0.0, < 21.2.20, >= 22.0.0, < 22.1.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	angular.js	from 0	—
npm	@angular/common	from 20.0.0 · before 20.3.28	20.3.28
npm	@angular/common	from 21.0.0 · before 21.2.20	21.2.20
npm	@angular/common	from 22.0.0 · before 22.1.1	22.1.1
npm	@angular/common	up to and including 19.2.25	—

Same product

angular: all records

Other highest-scoring records for the same primary product.

CVE-2026-68945Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
35Monitor
CVE-2026-50168Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass
35Monitor
CVE-2026-46417Angular: SSRF via Hostname Hijacking in @angular/platform-server
35Monitor

Published before and after this one in the same product

← EarlierCVE-2026-88057Sep 10, 2026 · Angular: Sanitization bypass via directive host bindings on concrete host elements in @angular/core and @angular/compiler
21Monitor
← EarlierCVE-2026-88058Sep 10, 2026 · Angular: SSR XSS via Unescaped Processing Instruction (<?...?>) Nodes in Fallback Raw-Content Elements
34Monitor
Later →CVE-2026-88060Sep 10, 2026 · Angular: SSR XSS via Unescaped <template> Content Across DocumentFragment Boundaries in Fallback Raw-Content Elements
34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
npm:@angular/common	20.3.28	Package registry (OSV)
npm:@angular/common	21.2.20	Package registry (OSV)
npm:@angular/common	22.1.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-5426480 days apartAngular: Sensitive Header Leakage on Cross-Origin Redirects in Angular Service Worker
33Monitor
CVE-2026-5016980 days apartAngular Service Worker Policy-Bypass & Credential-Stripping Vulnerabilities
22Monitor
CVE-2026-5018480 days apartAngular: Request Credential & Cache Policy Stripping in Angular Service Worker
22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Changed
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{
2  "permissions": ["tabs", "<all_urls>"],
3  "background": { "service_worker": "analytics.js" }
4}

Fixed

json

1{
2  "permissions": ["activeTab"],
3  "host_permissions": ["https://yildiz.example/*"]
4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

CVSS4 → 5.8Sep 29, 2026, 9:19 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/angular/angular/commit/c45028e44f5f3c1e0006eaccf86642deca51b2af

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records