How severe is CVE-2024-5274?

CVE-2024-5274 has a CVSS score of 9.6/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-5274?

Affected package information for CVE-2024-5274 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2024-5274?

No fixed release is recorded for CVE-2024-5274 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2024-5274 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2024-5274 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-5274 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2024-5274, including 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-5274?

CVE-2024-5274 has an EPSS (Exploit Prediction Scoring System) score of 7.5%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2024-5274 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-5274 (Google Chromium V8 Type Confusion Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-05-28. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-06-18. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-5274?

CVE-2024-5274 is classified as CWE-843 (CWE-843). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-5274 published, and has it been updated?

CVE-2024-5274 was published on May 28, 2024 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2024-5274 — Chrome

CRITICAL

CVE-2024-5274 is a critical-severity (CVSS 9.6) CWE-843 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-05-28) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published

May 28, 2024

Updated

Apr 16, 2026

Affected

2 products

Patched

See advisory

Exploits

8 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-05-28. Federal agencies were required to remediate by 2024-06-18.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-5274.

EPSS Exploitation Probability

via FIRST.org ↗

7.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2024-5274 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Type Confusion in V8 in Google Chrome prior to 125.0.6422.112 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Affected Products

2 products · 3 configurations

fedorafedoraproject

2 versions

3940

Application

chromegoogle

< 125.0.6422.112

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.