# CVE-2025-2336: AngularJS improper sanitization in SVG '' element with 'ngSanitize' > Attackers can bypass image source restrictions in AngularJS ngSanitize, enabling content spoofing and potential denial of service via malicious SVG images. - **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Jun 2025 - **Updated:** 3 Nov 2025 - **Also known as:** CLSA-2026-1775694723, CLSA-2026-1775694727, CLSA-2026-1781657704, CLSA-2026-1786355374, DEBIAN-CVE-2025-2336, GHSA-4p4w-6hg8-63wx, MINI-cr3f-f644-xmqr, ROOT-APP-NPM-CVE-2025-2336, UBUNTU-CVE-2025-2336 ## What is CVE-2025-2336? CVE-2025-2336 is a medium-severity cross-site scripting vulnerability in Google AngularJS, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Improper sanitization of the value of the 'href' and 'xlink:href' attributes in '' 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/Content_Spoofing  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 . Weakness: CWE-791 (Incomplete Filtering of Special Elements) ## Which versions are affected by CVE-2025-2336? 2 open source packages ship an affected version, including angular-sanitize. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `angular-sanitize` | npm | From 1.3.1 to 1.8.3 | None | | `angular-sanitize` | npm | From 1.3.1 to 1.8.3 | None | ## How do I fix CVE-2025-2336? Product is end of life, replace it. ## Is CVE-2025-2336 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2336 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-2336 and fix it if it is affected. What it is: CVE-2025-2336 is a medium-severity cross-site scripting vulnerability in Google AngularJS, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2336 exists. Affected packages and fixed versions: - angular-sanitize (npm): affected from 1.3.1 up to 1.8.3; no fix listed - angular-sanitize (npm): affected from 1.3.1 up to 1.8.3; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-2336/ (Markdown: https://insights.sbomify.com/CVE-2025-2336/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2336 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2336 - OSV: https://osv.dev/vulnerability/CVE-2025-2336 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-2336/ Summaries are generated and may contain mistakes; the official description above is the record.