Skip to main content
Mallory
← Back to News
internet-facing-service-vulnerabilitywidely-deployed-product-advisorycloud-service-vulnerability

Angular SSR Flaw Enables SSRF via Malformed URLs in Server-Side Rendering

Vulnerability Disclosure · 2 sources · Updated 5mo ago · First seen May 8, 2026

Angular SSR Flaw Enables SSRF via Malformed URLs in Server-Side Rendering

Angular disclosed a server-side request forgery (SSRF) issue in @angular/platform-server that affects applications using Server-Side Rendering. The flaw, tracked as CVE-2026-41423, stems from improper handling of protocol-relative and backslash-based URLs passed from server engines such as Express into Angular rendering functions. A crafted request can cause Angular to treat an attacker-controlled domain as the application's origin, allowing relative HttpClient requests and PlatformLocation.hostname references to resolve to external infrastructure.

The issue can expose internal services, including private APIs and cloud metadata endpoints, and related advisory material also links the bug family to header injection risks in Angular SSR deployments. Angular fixed the vulnerability in versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8, leaving earlier releases vulnerable where SSR is enabled and untrusted request paths can influence rendering context.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Feb 23, 2026 – May 8, 2026
  1. May 8, 20266mo ago

    Angular patches CVE-2026-41423 in multiple release branches

    Angular fixed an SSRF flaw in @angular/platform-server caused by improper handling of protocol-relative and backslash URLs in SSR contexts. The issue was patched in versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8.

    CVE-2026-41423 - Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
  2. Feb 23, 20269mo ago

    Angular discloses SSRF and header injection advisory for Angular SSR

    A GitHub security advisory was published for Angular SSR describing SSRF and header injection issues affecting Angular server-side rendering. The advisory is associated with angular/angular-cli.

    SSRF and Header Injection in Angular SSR · Advisory · angular/angular-cli · GitHub
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Angular
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.