CVE-2023-4762

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

CVSS: 8.8Highscored by CISA
Exploited in the wild: Yes, in CISA KEV since 6 Feb 2024CISA deadline for US federal agencies: 27 Feb 2024unvetted proof-of-concept code on github
EPSS: 41.4%chance of exploitation in the next 30 daystop 2% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 5 Sept 2023analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable: At runtime
Attack vector: network
Weakness: CWE-843 Common Weakness

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Product	Affected versions	Vendor says fixed in
Google Chrome	< 116.0.5845.179Vendor says fixed in: not stated	Not stated by the vendor

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

google:chrome
debian:debian_linux
fedoraproject:fedora
microsoft:edge_chromium

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack is delivered via a crafted HTML page loaded in the browser, which looks like a normal web page and does not contain unusual or easily distinguishable patterns that a web application firewall could reliably block without affecting legitimate users.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 6 Feb 2024.
CISA due date: 27 Feb 2024, the remediation deadline for US federal agencies
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code: Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
CISA SSVC: exploitation active, automatable no, technical impact totalAssessed by CISA 6 Feb 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

sherlocksecurity/CVE-2023-4762-Code-Review0 stars
zined/CVE-2023-47620 stars

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

5 Sept 2023Published
27 Sept 2023First proof-of-concept repository on GitHub (unvetted)21 days later
6 Feb 2024Added to CISA KEV (exploited in the wild)132 days (about 4 months) later
6 Feb 2024CISA SSVC assessment: exploitation activesame day later
27 Feb 2024CISA remediation due date (US federal agencies)21 days later
21 Oct 2025CVE record last updated603 days (about 2 years) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	RequiredA victim must click, open or otherwise cooperate.	A victim must click, open or otherwise cooperate.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2023-4762 being exploited?

Yes. CVE-2023-4762 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2023-4762?

CVE-2023-4762 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-4762?

Yes. A fix has been recorded for CVE-2023-4762. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-4762 affect?

CVE-2023-4762 affects google:chrome, debian:debian_linux, fedoraproject:fedora, microsoft:edge_chromium. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

11 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.