Security Resilience

CVE-2024-11919

Google Chrome ≤ 129.0.6668.58

Public PoC
Published
14 November 2025
Modified
02 October 2026
Patch / advisory
View advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS Score 0.0021 11th percentile
Risk Priority 35 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-11919 is a medium-severity User Interface (UI) Misrepresentation of Critical Information (CWE-451) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Inappropriate implementation in Intents in Google Chrome on Android prior to 129.0.6668.58 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)

CWE(s)
CWE-451

Related Threats

CVEs Like This One

CVE-2026-106317Same product: Google Android
CVE-2026-106305Same product: Google Android
CVE-2026-14134Same product: Google Android
CVE-2026-87624Same product: Google Android
CVE-2026-11215Same product: Google Android
CVE-2026-106338Same product: Google Android
CVE-2025-1922Same product: Google Android
CVE-2026-18007Same product: Google Android
CVE-2026-10984Same product: Google Android
CVE-2025-11213Same product: Google Android

Affected Assets

google
chrome
≤ 129.0.6668.58

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.6.3 Information security awareness, education and training partial match
blocks

A.6.3 is awareness/education/training that informs people of their responsibilities and improves skills; it does not stop a UI misrepresentation weakness from remaining present or from being exploitable (e.g. in phishing).

A.8.23 Web filtering partial match
degrades

Web filtering can block known phishing sites that exploit UI misrepresentation.

A.8.25 Secure development life cycle partial match
blocks

Secure development lifecycle includes UI/UX security requirements that can prevent misrepresentation of critical information.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including some that could indirectly relate to UI trustworthiness) be identified and specified during development; it does not itself enforce, implement, or stop UI misrepresentation from being exploitable.

A.8.28 Secure coding partial match
prevents

Secure coding practices can prevent UI flaws that obscure or spoof critical information.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can detect UI misrepresentation vulnerabilities before deployment.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-451, a class-level weakness, and none of its children carries one either.

References