Skip to content
major vulnerability· requires attention

Affects a widely-used web framework with high-severity SSRF; could disrupt many apps if unpatched.

Web

CVE-2026-50168

8.8
High
EPSS 0.24%Patch availableJun 24, 2026

Angular platform-server SSRF via malformed URL allows server-side requests to arbitrary endpoints.

common questions

Is CVE-2026-50168 being exploited?

Not confirmed. CVE-2026-50168 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-50168?

CVE-2026-50168 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-50168?

Yes. A fix has been recorded for CVE-2026-50168. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-50168 affect?

CVE-2026-50168 affects Angular platform-server (pre-fix versions). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-50168?

Upgrade to fixed versions (22.0.0-rc.2+; 21.2.15; 20.3.22; 19.2.23) and verify URL handling.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Angular platform-server (pre-fix versions)
impact

SSRF via malformed URL in Angular SSR HTTP requests; attacker can trigger server-side requests to internal or external endpoints.

action required

Patch when possible

affected versions
angular angular
  • affected>= 22.0.0-next.0 and < 22.0.0-rc.2
  • affected>= 21.0.0-next.0 and < 21.2.15
  • affected>= 20.0.0-next.0 and < 20.3.22
  • affected>= 19.0.0-next.0 and < 19.2.23
  • affected<= 18.2.14

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free