AngularJS Incomplete Filtering of Special Elements vulnerability

Exploitation

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

CVSS

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

EPSS

• CVE-2025-2336: 0.31% estimated exploitation activity in the next 30 days; percentile 24.03 (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.

Improper sanitization of the value of the 'href' and 'xlink:href' attributes in '<image' SVG elements in AngularJS's 'ngSanitize' module allows attackers to bypass common image source restrictions. This can lead to a form of Content Spoofing https://owasp.org/www-community/attacks/ContentSpoofing and also negatively affect the application's performance and behavior by using too large or slow-to-load images. This issue affects AngularJS versions greater than or equal to 1.3.1. Note: The AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see here https://docs.angularjs.org/misc/version-support-status .

Published by the source

4 Jun 2025, 18:30 UTC

Last modified by the source

3 Nov 2025, 21:35 UTC

Source last checked

26 Oct 2026, 12:38 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4p4w-6hg8-63wx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-4p4w-6hg8-63wx

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

# Patch Next advisory brief: CVE-2025-2336

Advisory: AngularJS Incomplete Filtering of Special Elements vulnerability
IDs: CVE-2025-2336, GHSA-4p4w-6hg8-63wx
Record: https://patchnext.com/advisories/cve-2025-2336 (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: Medium (CVSS 4.8)
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-sanitize: affected >= 1.3.1, <= 1.8.3

## Suggested inspection (read-only)
- `npm ls angular-sanitize --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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-sanitize.
- 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-4p4w-6hg8-63wx (OSV record GHSA-4p4w-6hg8-63wx lists affected ranges: npm angular-sanitize >=1.3.1 <=1.8.3)
- Verified: https://github.com/advisories/GHSA-4p4w-6hg8-63wx (GitHub-reviewed advisory GHSA-4p4w-6hg8-63wx lists affected ranges: npm angular-sanitize >=1.3.1 <=1.8.3)

Commands are suggestions: review each one before running it.