CVE-2025-2336VulnerabilityPublished 4 Jun 2025Updated 3 Nov 2025

CVE-2025-2336: Google AngularJS · Incomplete Filtering of Special Elements

Affects Google AngularJSSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium · end of life, no fix coming : replace or isolate Google AngularJS; no fix will be released.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

No fix will be released: Google AngularJS is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

Product	Affected	Fixed in
npmangularjs`pkg:npm/angularjs`Other threats	Affected >=1.3.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since AngularJS is end-of-life and no official patches are available, European organizations should prioritize migrating legacy AngularJS applications to modern, supported frameworks such as Angular (2+), React, or Vue.js. In the interim, developers should implement strict input validation and sanitization on the server side to complement client-side controls, ensuring that 'href' and 'xlink:href' attributes in SVG elements are restricted to trusted sources. Employing Content Security Policy (CSP) headers can help limit the domains from which images and other resources can be loaded, mitigating the risk of malicious content injection. Regular security audits and code reviews should focus on sanitization logic and SVG usage. Monitoring application performance metrics can help detect abnormal loading times indicative of exploitation attempts. Additionally, educating development teams about the risks of using deprecated frameworks and encouraging adoption of secure coding practices will reduce future vulnerabilities. Finally, organizations should maintain an incident response plan to address potential content spoofing or denial of service incidents swiftly.

Description

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/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 .

Impact

For European organizations, this vulnerability poses risks primarily in sectors with legacy web applications built on AngularJS, including government portals, financial services, healthcare, and critical infrastructure management systems. Content spoofing can undermine user trust, facilitate phishing attacks, and lead to misinformation or fraud. Performance degradation caused by maliciously large or slow-loading images can disrupt service availability, impacting business continuity and user experience. The inability to patch AngularJS due to its end-of-life status increases exposure duration and complicates remediation efforts. Organizations with public-facing web applications are particularly vulnerable to reputation damage and potential regulatory scrutiny under GDPR if user data or service integrity is compromised. The medium severity indicates that while the threat is not critical, it is significant enough to warrant prompt attention, especially given the ease of remote exploitation without authentication or user interaction. The impact on confidentiality is minimal, but integrity and availability risks can affect operational reliability and trustworthiness of affected applications.

Summary

CVE-2025-2336 identifies a vulnerability in the AngularJS framework, specifically in the ngSanitize module responsible for sanitizing HTML content. The issue arises from incomplete filtering of special elements, notably the 'href' and 'xlink:href' attributes within SVG <image> elements. Attackers can exploit this by injecting malicious or oversized image URLs that bypass AngularJS's sanitization checks, which are intended to restrict image sources to safe domains or formats. This bypass can lead to content spoofing, where attackers manipulate the visual content of a web application to mislead users, potentially facilitating phishing or social engineering attacks. Additionally, by referencing large or slow-loading images, attackers can degrade application performance or cause denial of service conditions. The vulnerability affects AngularJS versions 1.3.1 and above. Since AngularJS is officially end-of-life, no patches or updates will be provided by Google, leaving legacy applications exposed. The CVSS 3.1 score of 4.8 reflects a medium severity, with network attack vector, high attack complexity, no privileges or user interaction required, and impacts limited to integrity and availability but not confidentiality. No known exploits have been reported in the wild as of the publication date. Organizations relying on AngularJS for web applications should be aware that this vulnerability can be leveraged remotely without authentication, increasing its risk profile. The lack of vendor support necessitates alternative mitigation strategies such as code refactoring or migration to supported frameworks.

CWE-791Incomplete Filtering of Special Elements (opens in a new tab)
Base weakness
The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 02:30 UTC

WeaknessesCWE-791

Technical details

References

Community reviews

Related threats