CVE-2026-50168: Google Angular SSRF allowlist bypass in platform-server

CVE-2026-50168 · Severity: high · CVSS 3.1 · Published 2026-06-22

A vulnerability in the Angular web development framework's server-side rendering component could allow attackers to redirect internal server requests to malicious external servers. This occurs when the server incorrectly processes specially formatted web addresses, bypassing security filters intended to restrict communication to trusted domains. If exploited, sensitive information like session cookies or internal authorization tokens could be sent to an attacker, and the attacker could potentially inject malicious content into the website seen by other users.

Technologies: Google Platform-Server, @angular/platform-server (npm). Vendors: Google, npm.

Quick answers

Is CVE-2026-50168 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-50168 being exploited in the wild.
How severe is CVE-2026-50168?
High severity, with a CVSS score of 3.1, published 22 June 2026.
Which products and versions are affected?
Google Platform-Server >= 22.0.0-next.0, < 22.0.0-rc.2; >= 21.0.0-next.0, < 21.2.15; >= 20.0.0-next.0, < 20.3.22; >= 19.0.0-next.0, < 19.2.23; <= 18.2.14; @angular/platform-server (npm) SEMVER:introduced=22.0.0-next.0,fixed=22.0.0-rc.2.
Is there a fix for CVE-2026-50168?
Yes. @angular/platform-server (npm): upgrade to 22.0.0-rc.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50168 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-50168?
Check whether you run Google Platform-Server or @angular/platform-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • @angular/platform-server (npm): upgrade to 22.0.0-rc.2 or later
    npm install @angular/platform-server@22.0.0-rc.2

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in @angular/platform-server due to a parser differential between the strict WHATWG URL parser (used for allowlist validation) and the lenient Domino URL parser (used for DOM emulation). When an attacker provides a malformed URL with a double port structure (e.g., 'evil.com:80:80'), Node's strict parser fails validation and skips host checks, while the lenient parser accepts it and resolves the origin to the attacker's domain. The 'relativeUrlsTransformerInterceptorFn' then resolves relative backend API calls against this malicious origin. This allows attackers to intercept outgoing requests containing sensitive credentials or perform response injection. The issue is fixed in versions 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.

Affected products

  • Google Angular < 19.2.23, >= 19.0.0-next.0 < 19.2.23, >= 20.0.0-next.0 < 20.3.22, >= 21.0.0-next.0 < 21.2.15, >= 22.0.0-next.0 < 22.0.0-rc.2

Identifiers

  • CVE-2026-50168
  • GHSA-xrxm-cp7j-8xf6

Timeline

  • 2026-05-26: other: Fix PR submitted to GitHub
  • 2026-05-28: advisory: GitHub Security Advisory published
  • 2026-06-22: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.