CVE-2026-41423
SSRF in Angular platform-server during SSR redirects to attacker domain.
Is CVE-2026-41423 being exploited?
Not confirmed. CVE-2026-41423 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-41423?
CVE-2026-41423 is rated High with a CVSS score of 8.7. 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-41423?
Yes. A fix has been recorded for CVE-2026-41423. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41423 affect?
CVE-2026-41423 affects Angular platform-server (@angular/platform-server). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41423?
Upgrade to patched platform-server versions: 19.2.21+, 20.3.19+, 21.2.9, 22.0.0-next.8
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SSRF allows access to internal APIs/metadata by redirecting host-origin requests to attacker-controlled domain.
Patch when possible
- affected< 19.2.21
- affected>= 20.0.0-next.0 and < 20.3.19
- affected>= 21.0.0-next.0 and < 21.2.9
- affected>= 22.0.0-next.0 and < 22.0.0-next.8
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.