Type confusion in V8 in Google Chrome prior to 112.0.5615.121 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
CVE-2023-2033
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-04-17), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 41%
- EPSS %ILE
- 99%
- KEV
- ⚠ Exploited
Published
April 14, 2023
Last Modified
October 24, 2025
Advisory Details (9)
Auto-updated Jun 2, 2026Chromium, Google Chrome, Microsoft Edge: Multiple Vulnerabilities (GLSA 202309-17) — Gentoo security
https://security.gentoo.org/glsa/202309-17[SECURITY] Fedora 37 Update: chromium-112.0.5615.165-1.fc37 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/[email protected]/message/SLO7BL2MHZYPY6O3OAEAQL3SKYMGGO6M/[SECURITY] Fedora 37 Update: chromium-112.0.5615.121-2.fc37 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/[email protected]/message/RJQI63HWZFL6M26Q6UOHKDY6LD2PFC5Z/[SECURITY] Fedora 36 Update: chromium-112.0.5615.165-1.fc36 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/[email protected]/message/IHHD6KNH4WLUE6JG6HRQZWNAJMHJ32X7/[SECURITY] Fedora 38 Update: chromium-112.0.5615.121-2.fc38 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/[email protected]/message/FEJZMAUB4XP44HSHEBDWEKFGA7DUHY42/[SECURITY] Fedora 38 Update: chromium-112.0.5615.165-1.fc38 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/[email protected]/message/ES2CDRHR2Y4WY6DNDIAPYZFXJU3ZBFAV/[SECURITY] Fedora 36 Update: chromium-112.0.5615.121-2.fc36 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/[email protected]/message/4AOSGAOPXLBK4A5ZRTVZ4M6QKVLSWMWG/Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2023/04/stable-channel-update-for-desktop_14.htmlAffected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (95 versions) | 112.0.5615.121-1~deb11u1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 112.0.5615.121-1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 112.0.5615.121-1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 112.0.5615.121-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 95× in last 7d / 395× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,302 total refreshes for this CVE.
- 2026-09-08 14:49 UTCVendor advisory
- 2026-09-08 14:48 UTCGHSA enrichment
- 2026-09-08 10:40 UTCVendor advisory
- 2026-09-08 10:40 UTCGHSA enrichment
- 2026-09-08 06:31 UTCVendor advisory
- 2026-09-08 06:31 UTCGHSA enrichment
- 2026-09-08 02:23 UTCVendor advisory
- 2026-09-08 02:23 UTCGHSA enrichment
- 2026-09-07 22:16 UTCVendor advisory
- 2026-09-07 22:16 UTCGHSA enrichment
- 2026-09-07 18:09 UTCEG score recompute
- 2026-09-07 18:09 UTCVendor advisory
- 2026-09-07 18:09 UTCGHSA enrichment
- 2026-09-07 15:59 UTCEPSS rescore
- 2026-09-07 14:02 UTCVendor advisory
- 2026-09-07 14:02 UTCGHSA enrichment
- 2026-09-07 09:54 UTCVendor advisory
- 2026-09-07 09:53 UTCGHSA enrichment
- 2026-09-07 05:45 UTCVendor advisory
- 2026-09-07 05:45 UTCGHSA enrichment
- 2026-09-07 01:37 UTCVendor advisory
- 2026-09-07 01:37 UTCGHSA enrichment
- 2026-09-06 21:30 UTCVendor advisory
- 2026-09-06 21:30 UTCGHSA enrichment
- 2026-09-06 17:23 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-06 17:23 UTCVendor advisory
- 2026-09-06 17:23 UTCGHSA enrichment
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 13:15 UTCVendor advisory
- 2026-09-06 13:15 UTCGHSA enrichment
- 2026-09-06 09:08 UTCVendor advisory
- 2026-09-06 09:08 UTCGHSA enrichment
- 2026-09-06 04:58 UTCVendor advisory
- 2026-09-06 04:58 UTCGHSA enrichment
- 2026-09-06 00:51 UTCVendor advisory
- 2026-09-06 00:51 UTCGHSA enrichment
- 2026-09-05 20:42 UTCVendor advisory
- 2026-09-05 20:42 UTCGHSA enrichment
- 2026-09-05 16:35 UTCEG score recompute
- 2026-09-05 16:35 UTCVendor advisory
- 2026-09-05 16:35 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 12:27 UTCVendor advisory
- 2026-09-05 12:27 UTCGHSA enrichment
- 2026-09-05 08:17 UTCVendor advisory
- 2026-09-05 08:17 UTCGHSA enrichment
- 2026-09-05 04:10 UTCVendor advisory
- 2026-09-05 04:09 UTCGHSA enrichment
- 2026-09-05 00:02 UTCVendor advisory
- 2026-09-05 00:02 UTCGHSA enrichment
- 2026-09-04 19:54 UTCVendor advisory
- 2026-09-04 19:53 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 15:43 UTCEG score recompute
- 2026-09-04 15:43 UTCVendor advisory
- 2026-09-04 15:43 UTCGHSA enrichment
- 2026-09-04 13:58 UTCEPSS rescore
- 2026-09-04 11:36 UTCVendor advisory
- 2026-09-04 11:36 UTCGHSA enrichment
- 2026-09-04 07:29 UTCEG score recompute
- 2026-09-04 07:29 UTCVendor advisory
- 2026-09-04 07:29 UTCGHSA enrichment
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-04 03:22 UTCVendor advisory
- 2026-09-04 03:21 UTCGHSA enrichment
- 2026-09-03 23:14 UTCVendor advisory
- 2026-09-03 23:14 UTCGHSA enrichment
- 2026-09-03 19:07 UTCVendor advisory
- 2026-09-03 19:07 UTCGHSA enrichment
- 2026-09-03 15:00 UTCVendor advisory
- 2026-09-03 15:00 UTCGHSA enrichment
- 2026-09-03 10:53 UTCVendor advisory
- 2026-09-03 10:52 UTCGHSA enrichment
- 2026-09-03 06:43 UTCVendor advisory
- 2026-09-03 06:42 UTCGHSA enrichment
- 2026-09-03 02:32 UTCVendor advisory
- 2026-09-03 02:32 UTCGHSA enrichment
- 2026-09-02 22:24 UTCVendor advisory
- 2026-09-02 22:24 UTCGHSA enrichment
- 2026-09-02 18:17 UTCEG score recompute
- 2026-09-02 18:16 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-02 14:08 UTCVendor advisory
- 2026-09-02 14:08 UTCGHSA enrichment
- 2026-09-02 10:01 UTCVendor advisory
- 2026-09-02 10:01 UTCGHSA enrichment
- 2026-09-02 05:51 UTCVendor advisory
- 2026-09-02 05:50 UTCGHSA enrichment
- 2026-09-02 01:40 UTCVendor advisory
- 2026-09-02 01:39 UTCGHSA enrichment
- 2026-09-01 21:32 UTCVendor advisory
- 2026-09-01 21:32 UTCGHSA enrichment
- 2026-09-01 17:25 UTCVendor advisory
- 2026-09-01 17:25 UTCGHSA enrichment
- 2026-09-01 13:19 UTCVendor advisory
- 2026-09-01 13:18 UTCGHSA enrichment
- 2026-09-01 09:11 UTCVendor advisory
- 2026-09-01 09:11 UTCGHSA enrichment
- 2026-09-01 05:02 UTCEG score recompute
Publicly available exploits
(3 references)Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Open source ↗GitHub PoCmistymntncop/CVE-2023-2033First seen Aug 2, 2023
- GitHub PoCsandumjacob/CVE-2023-2033-AnalysisFirst seen Apr 26, 2023
A collection of resources and information about CVE-2023-2033
Open source ↗ - GitHub PoCinsoxin/CVE-2023-2033First seen Apr 17, 2023
Reproduce CVE-2023-2033
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-843
- CVE-2010-2299EG 10.0HIGH
- CVE-2016-1000005EG 9.8CRITICAL
- CVE-2018-4920NVD 8.8EG 9.8EPSS p94CRITICAL
- CVE-2016-6992NVD 8.8EG 9.8EPSS p93CRITICAL
- CVE-2012-0507EG 9.8 KEVEPSS p100CRITICAL
- CVE-2012-0752EG 9.3EPSS p95HIGH
- CVE-2017-5070NVD 8.8EG 9.0 KEVEPSS p98CRITICAL
- CVE-2017-11292NVD 8.8EG 9.0 KEVEPSS p96CRITICAL
- CVE-2017-8291NVD 7.8EG 9.0 KEVEPSS p100CRITICAL
- CVE-2017-0037NVD 8.1EG 9.0 KEVEPSS p100CRITICAL
Frequently asked(6)
What is CVE-2023-2033?
When was CVE-2023-2033 disclosed?
Is CVE-2023-2033 actively exploited?
What is the CVSS score of CVE-2023-2033?
Which products are affected by CVE-2023-2033?
How do I remediate CVE-2023-2033?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-2033
Is Your Infrastructure Affected by CVE-2023-2033?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.