VulnerabilityPublished 21 May 2014Updated 4 Jun 2025

CVE-2014-1745: SVG implementation · Use After Free

Source CVE Database V5

Not known to be exploited · CVSS 7.1 High · fixed in 35.0.1916.114 : patch affected systems soon.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score

7.1High

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

EPSS: 1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 35.0.1916.114

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 21 May 2014
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
n/a n/a	Affected <35.0.1916.114	Fixed in 35.0.1916.114

AI-suggested

Immediate upgrade to the latest version of Google Chrome, as versions 35.0.1916.114 and later contain the fix for this vulnerability.
Implement browser update policies within organizations to ensure all endpoints receive timely security patches, minimizing exposure to legacy vulnerabilities.
Employ web filtering and email security solutions to block or flag potentially malicious SVG content or attachments, reducing the risk of user interaction with crafted exploits.
Educate users on the risks of interacting with unsolicited or suspicious web content and attachments, emphasizing caution with SVG files or links from unknown sources.
For environments where updating Chrome is not immediately feasible, consider restricting or sandboxing browser usage, or using alternative browsers not affected by this vulnerability.
Monitor network traffic for unusual patterns that may indicate attempts to deliver malicious SVG payloads.
Conduct regular vulnerability assessments and penetration testing to identify and remediate outdated software versions across the organization.

Description

Use-after-free vulnerability in the SVG implementation in Blink, as used in Google Chrome before 35.0.1916.114, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors that trigger removal of an SVGFontFaceElement object, related to core/svg/SVGFontFaceElement.cpp.

Impact

For European organizations, the primary impact of CVE-2014-1745 lies in the potential for denial of service attacks against users running vulnerable versions of Google Chrome. This could disrupt business operations, especially in sectors reliant on web-based applications and services. Although the vulnerability could theoretically lead to more severe consequences like remote code execution, no confirmed exploits have been observed, reducing immediate risk. However, organizations with legacy systems or those unable to update browsers promptly remain at risk. Confidential data confidentiality could be compromised if an advanced exploit were developed, posing risks to sensitive information handled by European enterprises. Additionally, denial of service conditions could affect availability of critical web services or internal applications accessed via Chrome. Given the widespread use of Chrome across Europe, especially in corporate and governmental environments, unpatched systems could be targeted by attackers leveraging crafted SVG content delivered via email, websites, or other vectors. The requirement for user interaction means phishing or social engineering could be used to trigger exploitation. Overall, the threat emphasizes the importance of maintaining up-to-date browsers to protect against memory corruption vulnerabilities that could impact confidentiality and availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 02:26 UTC

WeaknessesCWE-399

Technical details

References

Community reviews

Related threats