dbcve.org
AngularFramework / library

CVE-2026-50168

HIGH · 8.2 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 19.2.23 / 20.3.22 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, an issue in the @angular/platform-server package allows remote attackers to bypass host allowlist constraints and direct server-side outgoing requests to arbitrary external endpoints. This occurs due to a parser differential between the strict WHATWG URL parser used for allowlist validation and the lenient Domino URL parser used to initialize the server emulated DOM. When a server-side request contains a malformed URL with a double port structure (e.g., http://evil.com:80:80/path), Node's strict URL.canParse(url) logic returns false and skips host check validation entirely. However, the same malformed URL is later accepted and parsed leniently by Domino's internal parser, which resolves the origin to http://evil.com:80. The Angular SSR HTTP request interceptor (relativeUrlsTransformerInterceptorFn) then resolves all relative backend HTTP requests against this adopted origin, executing the SSRF attack. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Angular SSR vulnerability allows SSRF attacks via a parser differential between strict WHATWG URL validation and lenient Domino URL parsing. Malformed URLs with double port structures (e.g., http://evil.com:80:80/path) bypass allowlist checks because Node's strict URL.canParse() returns false, but Domino resolves to http://evil.com:80, enabling attackers to direct server-side outgoing requests to arbitrary endpoints.

MitigationUpgrade Angular to version 22.0.0-rc.2, 21.2.15, 20.3.22, or 19.2.23 or later to patch the @angular/platform-server package.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AngularFramework / library
Affected:>= 2.0.0, <= 18.2.14>= 19.0.0, < 19.2.23>= 20.0.0, < 20.3.22>= 21.0.0, < 21.2.15= 22.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Angular framework version
    Run 'ng version' or inspect package.json for '@angular/core' version
    Affected if Version is >= 2.0.0 and <= 18.2.14, OR >= 19.0.0 and < 19.2.23, OR >= 20.0.0 and < 20.3.22, OR >= 21.0.0 and < 21.2.15, OR equals 22.0.0
  2. Verify @angular/platform-server is installed
    Inspect package.json or run 'npm list @angular/platform-server' to confirm the SSR package is present
    Affected if @angular/platform-server is listed as a dependency in package.json
  3. Confirm SSR is enabled in the application
    Check for server.ts file, or look for 'provideServerRendering' in app.config.ts, or check for @angular/platform-server imports in the codebase
    Affected if SSR rendering is configured and active in the application
  4. Identify URL allowlist validation logic
    Search source code for patterns like 'canParse', 'url.canParse', allowlist, or custom URL validation functions that validate outgoing request targets
    Affected if The application uses URL.canParse() or similar strict validation for allowlisting outgoing request destinations

The environment is affected if Angular version falls within the affected ranges AND @angular/platform-server is installed with SSR enabled AND the application validates outgoing request URLs using strict parsing that could be bypassed by malformed double-port URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 19.2.23 / 20.3.22 / 21.2.15 or later
Fixed in 19.2.2320.3.2221.2.15
Vendor patch github.com →
Interim mitigation

Upgrade Angular to version 22.0.0-rc.2, 21.2.15, 20.3.22, or 19.2.23 or later to patch the @angular/platform-server package.

Recommended fix High confidence

19.2.23 (for 18.x/19.x), 20.3.22 (for 20.x), 21.2.15 (for 21.x), or 22.0.0-rc.2 (for 22.x)

  1. Identify the current Angular version in your project by running `ng version` or checking package.json
  2. Upgrade to a fixed version based on your current major version:
  3. - If on Angular 18.x: `npm install @angular/[email protected] @angular/[email protected] @angular/[email protected] @angular/[email protected]` (or upgrade to 19.x latest)
  4. - If on Angular 19.x: `npm install @angular/[email protected] @angular/[email protected] @angular/[email protected] @angular/[email protected]`
  5. - If on Angular 20.x: `npm install @angular/[email protected] @angular/[email protected] @angular/[email protected] @angular/[email protected]`
  6. - If on Angular 21.x: `npm install @angular/[email protected] @angular/[email protected] @angular/[email protected] @angular/[email protected]`
  7. - If on Angular 22.x: `npm install @angular/[email protected] @angular/[email protected] @angular/[email protected] @angular/[email protected]`
  8. Run `npm install` to update all dependencies
Caveat Major version upgrades (e.g., 18 to 19, 19 to 20) may introduce breaking changes; review Angular's update guide at update.angular.io

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Angular Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50168 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data