Skip to main content
Mallory
HighVulnerability

CVE-2026-50168: SSRF allowlist bypass in Angular @angular/platform-server

Published Jun 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v4
EPSS0.24%15th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
AngularAngularjs
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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim 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.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
FAQ

Frequently asked questions

Is CVE-2026-50168 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-50168 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-50168?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-50168.
Is there a patch for CVE-2026-50168?
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.
What products are affected by CVE-2026-50168?
Angular and Angularjs Angular.Js.
How severe is CVE-2026-50168?
CVE-2026-50168 has a CVSS v4 score of 8.8 (High) and an EPSS score of 0.24% (15th percentile) as of Sep 25, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.