CVE-2022-4262

Type confusion in V8 in Google Chrome prior to 108.0.5359.94 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

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

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable: At runtime
Attack vector: network
Weakness: CWE-843 Common Weakness
Can a WAF block it?: No. See why

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	< 108.0.5359.94Vendor 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

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 is an HTTP request. The malicious input looks like normal web content, so a web application firewall cannot reliably distinguish it from legitimate pages.

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 5 Dec 2022.
CISA due date: 26 Dec 2022, the remediation deadline for US federal agencies
CISA required action: Apply updates per vendor instructions.
Public exploit code: Unvetted proof-of-concept code on GitHub: 3 GitHub proofs of concept
CISA SSVC: exploitation active, automatable no, technical impact totalAssessed by CISA 28 Jan 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

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

2 Dec 2022Published
5 Dec 2022Added to CISA KEV (exploited in the wild)2 days later
26 Dec 2022CISA remediation due date (US federal agencies)21 days later
13 Jul 2023First proof-of-concept repository on GitHub (unvetted)199 days (about 7 months) later
28 Jan 2025CISA SSVC assessment: exploitation active566 days (about 2 years) later
21 Oct 2025CVE record last updated266 days (about 9 months) 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-2022-4262 being exploited?

Yes. CVE-2022-4262 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-2022-4262?

CVE-2022-4262 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-2022-4262?

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

What does CVE-2022-4262 affect?

CVE-2022-4262 affects google:chrome. 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

3 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.