CVE-2024-13178VulnerabilityPublished 14 Nov 2025

CVE-2024-13178: Google Chrome · Inappropriate implementation

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 128.0.6613.84 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
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: None: There is no loss of confidentiality within the impacted component.
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 14 Nov 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

Upgrade Google Chrome to 128.0.6613.84.

Affected software

Product	Affected	Fixed in
Google Chrome	Affected =128.0.6613.84 <128.0.6613.84	Fixed in 128.0.6613.84

AI-suggested

1. Ensure all Chrome installations are updated to version 128.0.6613.84 or later, where the vulnerability is addressed. 2. Implement enterprise browser management policies to restrict fullscreen mode usage on untrusted or unknown websites, reducing the attack surface. 3. Educate users about the risks of fullscreen prompts and encourage skepticism of unexpected fullscreen requests, especially from unfamiliar sites. 4. Deploy web filtering solutions to block access to known malicious or suspicious websites that could exploit this vulnerability. 5. Monitor browser behavior for unusual fullscreen activity or UI anomalies that could indicate exploitation attempts. 6. Integrate multi-factor authentication (MFA) to mitigate risks from potential phishing attacks facilitated by UI spoofing. 7. Coordinate with IT and security teams to include this vulnerability in vulnerability management and incident response plans. 8. Stay informed about any new patches or advisories from Google regarding this issue.

Description

Inappropriate implementation in Fullscreen in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

Impact

For European organizations, this vulnerability primarily poses a risk of UI spoofing attacks that can facilitate phishing and social engineering, potentially leading to credential theft or unauthorized actions by deceived users. While it does not directly compromise data confidentiality or integrity, the resulting user confusion can indirectly lead to security breaches. The availability impact is limited to possible browser crashes or disruptions caused by malicious pages exploiting the fullscreen flaw. Sectors with high reliance on web applications, such as finance, government, and critical infrastructure, could face increased risk if attackers leverage this vulnerability to impersonate trusted interfaces. The medium severity rating indicates a moderate risk that should not be ignored, especially in environments with high user interaction with web content. The absence of known exploits in the wild reduces immediate urgency but does not eliminate the threat, as attackers may develop exploits over time. European organizations with large user bases on Chrome should prioritize patching and user awareness to reduce exposure.

CWE-451User Interface (UI) Misrepresentation of Critical Information (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks.
Implementation · Input Validation
Perform data validation (e.g. syntax, length, etc.) before interpreting the data.
Architecture and Design · Output Encoding
Create a strategy for presenting information, and plan for how to display unusual characters.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Spear Phishing (opens in a new tab)
Mobile Phishing (opens in a new tab)
Phishing (opens in a new tab)
Resource Location Spoofing (opens in a new tab)
Action Spoofing (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 21 Nov 2025, 04:51 UTC

WeaknessesCWE-451

Technical details

References

Community reviews

Related threats