High

SSRF allowlist bypass in Angular @angular/platform-server

IdentifiersCVE-2026-50168CWE-918· Server-Side Request Forgery (SSRF)

CVE-2026-50168 is a server-side request forgery vulnerability in Angular's @angular/platform-server package affecting versions prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23. The flaw is caused by a parser differential between the strict WHATWG URL parser used by Node/Angular for allowlist validation and the more lenient Domino URL parser used to initialize the server-emulated DOM during SSR. A malformed absolute URL with a double-port structure, such as http://evil.com:80:80/path, causes URL.canParse(url) to return false, which results in host allowlist validation being skipped. The same malformed URL is later accepted by Domino's parser and normalized to an attacker-controlled origin such as http://evil.com:80. Angular's SSR HTTP request interceptor, relativeUrlsTransformerInterceptorFn, then resolves relative backend HTTP requests against that adopted origin, enabling attacker-directed outbound server-side requests.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to bypass host allowlist restrictions in Angular SSR deployments and redirect server-side outbound requests to arbitrary external endpoints. This can expose sensitive data carried in SSR-initiated backend requests, including credentials, session cookies, and authorization tokens, depending on application behavior. The advisory also indicates potential response or content poisoning, because attacker-controlled responses may be incorporated into the emulated DOM and influence rendered HTML returned to users.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, avoid reconstructing SSR request URLs from untrusted raw Host headers or absolute-form request URIs, and do not pass such untrusted values as config.url to renderApplication or renderModule. Avoid relative outbound backend HTTP requests that depend on SSR base-URL rewriting. Enforce strict upstream validation and normalization of Host headers and request URIs before SSR processing so malformed absolute URLs cannot influence origin selection.

Remediation

Patch, then assume compromise.

Upgrade @angular/platform-server to a fixed release appropriate for the deployed major version: 22.0.0-rc.2, 21.2.15, 20.3.22, or 19.2.23.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

AngularAngularapplication

AngularjsAngular.Jsapplication

GooglePlatform-Serverapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app

cvefeed high severityNews

Jun 22, 2026

CVE-2026-50168 - Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass

An SSRF allowlist bypass vulnerability in Angular's @angular/platform-server caused by a parser differential between the WHATWG URL parser and Domino URL parser, allowing malformed URLs to bypass host validation and influence server-side outgoing requests.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1