angular vulnerable to super-linear runtime due to backtracking

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-21490: 1.89% estimated exploitation activity in the next 30 days; percentile 79.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

This affects versions of the package angular from 1.3.0. A regular expression used to split the value of the ng-srcset directive is vulnerable to super-linear runtime due to backtracking. With a large carefully-crafted input, this can result in catastrophic backtracking and cause a denial of service. Note: This package is EOL and will not receive any updates to address this issue. Users should migrate to @angular/core.

Published by the source

10 Feb 2024, 06:30 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:38 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4w4v-5hc9-xrr2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4w4v-5hc9-xrr2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-21490

Advisory: angular vulnerable to super-linear runtime due to backtracking
IDs: CVE-2024-21490, GHSA-4w4v-5hc9-xrr2
Record: https://patchnext.com/advisories/cve-2024-21490 (revision 2, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm angular: affected >= 1.3.0, <= 1.8.3
- Maven org.webjars.npm:angular: affected >= 1.3.0, <= 1.8.3
- Maven org.webjars.bower:angular: affected >= 1.3.0, <= 1.8.3

## Suggested inspection (read-only)
- `npm ls angular --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- Maven org.webjars.npm:angular: check the installed version with your package manager.
- Maven org.webjars.bower:angular: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on angular, org.webjars.npm:angular, org.webjars.bower:angular.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4w4v-5hc9-xrr2 (OSV record GHSA-4w4v-5hc9-xrr2 lists affected ranges: npm angular >=1.3.0 =1.3.0 =1.3.0 <=1.8.3)
- Verified: https://github.com/advisories/GHSA-4w4v-5hc9-xrr2 (GitHub-reviewed advisory GHSA-4w4v-5hc9-xrr2 lists affected ranges: npm angular >=1.3.0 =1.3.0 =1.3.0 <=1.8.3)

Commands are suggestions: review each one before running it.