The issue was addressed with improved checks. This issue is fixed in macOS Sonoma 14. Processing web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited against versions of iOS before iOS 16.7.
CVE-2023-41993
Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-09-25), 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)
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 9.8(high)
- EG Risk
- 84(Attend)EG Risk 84/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 computedSeverity98% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 29%
- EPSS %ILE
- 98%
- KEV
- ⚠ Exploited
Published
September 21, 2023
Last Modified
June 17, 2026
Advisory Details (7)
Auto-updated Jun 2, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-41993WebKitGTK and WPE WebKit Security Advisory WSA-2023-0009 - The WebKitGTK Project
https://webkitgtk.org/security/WSA-2023-0009.htmlAbout the security content of Safari 16.6.1 - Apple Support
https://support.apple.com/kb/HT213930About the security content of iOS 17.0.1 and iPadOS 17.0.1 - Apple Support
https://support.apple.com/kb/HT213926About the security content of macOS Sonoma 14 - Apple Support
https://support.apple.com/en-us/HT213940WebKitGTK+: Multiple Vulnerabilities (GLSA 202401-33) — Gentoo security
https://security.gentoo.org/glsa/202401-33Vendor Advisories for CVE-2023-41993(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(4)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | webkit2gtk-driver (2.42.1-0ubuntu0.23.04.1) @ lunar | 2026-09-08 | ubuntu |
| redhat | webkitgtk4-0:2.48.3-2.el7_9 | 2025-07-07 | redhat |
| redhat | webkit2gtk3-0:2.38.5-1.el9_2.3 | 2023-07-18 | redhat |
| redhat | webkit2gtk3-0:2.38.5-1.el8_8.5 | 2023-07-18 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(8 across 4 ecosystems)
Debian:11(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| webkit2gtk | 2.32.3-1 ... 2.42.1-1~bpo12+1 (109 versions) | 2.42.1-1~deb11u1 | — |
| wpewebkit | 2.32.3-2 ... 2.52.5-1 (90 versions) | — | — |
Debian:12(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| webkit2gtk | 2.40.1-1 ... 2.42.1-1~deb11u2 (26 versions) | 2.42.1-1~deb12u1 | — |
| wpewebkit | 2.38.6-1 ... 2.52.5-1 (53 versions) | — | — |
Debian:13(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| webkit2gtk | — | 2.42.1-1 | — |
| wpewebkit | — | 2.42.1-1 | — |
Debian:14(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| webkit2gtk | — | 2.42.1-1 | — |
| wpewebkit | — | 2.42.1-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 95× in last 7d / 414× 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,344 total refreshes for this CVE.
- 2026-09-08 06:29 UTCVendor advisory
- 2026-09-08 06:29 UTCGHSA enrichment
- 2026-09-08 02:19 UTCVendor advisory
- 2026-09-08 02:19 UTCGHSA enrichment
- 2026-09-07 22:10 UTCVendor advisory
- 2026-09-07 22:10 UTCGHSA enrichment
- 2026-09-07 18:01 UTCVendor advisory
- 2026-09-07 18:01 UTCGHSA enrichment
- 2026-09-07 13:51 UTCVendor advisory
- 2026-09-07 13:51 UTCGHSA enrichment
- 2026-09-07 09:38 UTCVendor advisory
- 2026-09-07 09:38 UTCGHSA enrichment
- 2026-09-07 05:28 UTCVendor advisory
- 2026-09-07 05:28 UTCGHSA enrichment
- 2026-09-07 01:20 UTCVendor advisory
- 2026-09-07 01:20 UTCGHSA enrichment
- 2026-09-06 21:09 UTCVendor advisory
- 2026-09-06 21:08 UTCGHSA enrichment
- 2026-09-06 16:58 UTCEG score recompute
- 2026-09-06 16:58 UTCVendor advisory
- 2026-09-06 16:58 UTCGHSA enrichment
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 12:48 UTCVendor advisory
- 2026-09-06 12:48 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-06 08:39 UTCVendor advisory
- 2026-09-06 08:39 UTCGHSA enrichment
- 2026-09-06 04:30 UTCVendor advisory
- 2026-09-06 04:30 UTCGHSA enrichment
- 2026-09-06 00:21 UTCVendor advisory
- 2026-09-06 00:21 UTCGHSA enrichment
- 2026-09-05 20:09 UTCVendor advisory
- 2026-09-05 20:09 UTCGHSA enrichment
- 2026-09-05 16:00 UTCEG score recompute
- 2026-09-05 16:00 UTCVendor advisory
- 2026-09-05 16:00 UTCGHSA enrichment
- 2026-09-05 15:26 UTCEPSS rescore
- 2026-09-05 11:51 UTCVendor advisory
- 2026-09-05 11:50 UTCGHSA enrichment
- 2026-09-05 07:38 UTCVendor advisory
- 2026-09-05 07:38 UTCGHSA enrichment
- 2026-09-05 03:29 UTCVendor advisory
- 2026-09-05 03:29 UTCGHSA enrichment
- 2026-09-04 23:20 UTCVendor advisory
- 2026-09-04 23:20 UTCGHSA enrichment
- 2026-09-04 19:09 UTCVendor advisory
- 2026-09-04 19:09 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 15:00 UTCEG score recompute
- 2026-09-04 15:00 UTCVendor advisory
- 2026-09-04 15:00 UTCGHSA enrichment
- 2026-09-04 13:58 UTCEPSS rescore
- 2026-09-04 10:49 UTCVendor advisory
- 2026-09-04 10:49 UTCGHSA enrichment
- 2026-09-04 06:39 UTCEG score recompute
- 2026-09-04 06:39 UTCVendor advisory
- 2026-09-04 06:38 UTCGHSA enrichment
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-04 02:26 UTCVendor advisory
- 2026-09-04 02:26 UTCGHSA enrichment
- 2026-09-03 22:14 UTCVendor advisory
- 2026-09-03 22:14 UTCGHSA enrichment
- 2026-09-03 18:04 UTCVendor advisory
- 2026-09-03 18:03 UTCGHSA enrichment
- 2026-09-03 13:52 UTCVendor advisory
- 2026-09-03 13:52 UTCGHSA enrichment
- 2026-09-03 09:42 UTCVendor advisory
- 2026-09-03 09:42 UTCGHSA enrichment
- 2026-09-03 05:33 UTCVendor advisory
- 2026-09-03 05:33 UTCGHSA enrichment
- 2026-09-03 01:22 UTCVendor advisory
- 2026-09-03 01:22 UTCGHSA enrichment
- 2026-09-02 21:13 UTCVendor advisory
- 2026-09-02 21:13 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 17:03 UTCEG score recompute
- 2026-09-02 17:03 UTCVendor advisory
- 2026-09-02 17:03 UTCGHSA enrichment
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-02 12:54 UTCVendor advisory
- 2026-09-02 12:54 UTCGHSA enrichment
- 2026-09-02 08:45 UTCVendor advisory
- 2026-09-02 08:45 UTCGHSA enrichment
- 2026-09-02 04:35 UTCVendor advisory
- 2026-09-02 04:35 UTCGHSA enrichment
- 2026-09-02 00:26 UTCVendor advisory
- 2026-09-02 00:26 UTCGHSA enrichment
- 2026-09-01 20:16 UTCVendor advisory
- 2026-09-01 20:16 UTCGHSA enrichment
- 2026-09-01 16:07 UTCEG score recompute
- 2026-09-01 16:07 UTCVendor advisory
- 2026-09-01 16:07 UTCGHSA enrichment
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-09-01 11:57 UTCVendor advisory
- 2026-09-01 11:57 UTCGHSA enrichment
- 2026-09-01 07:46 UTCEG score recompute
- 2026-09-01 07:46 UTCVendor advisory
- 2026-09-01 07:46 UTCGHSA enrichment
- 2026-09-01 03:34 UTCVendor advisory
- 2026-09-01 03:34 UTCGHSA enrichment
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.
- GitHub PoChrtowii/cve-2023-41993-testFirst seen Oct 16, 2023
testing poc
Open source ↗ - GitHub PoC0x06060606/CVE-2023-41993First seen Oct 16, 2023
CVE-2023-41993
Open source ↗ - Open source ↗GitHub PoCpo6ix/POC-for-CVE-2023-41993First seen Oct 15, 2023
Frequently asked(6)
What is CVE-2023-41993?
When was CVE-2023-41993 disclosed?
Is CVE-2023-41993 actively exploited?
What is the CVSS score of CVE-2023-41993?
Which products are affected by CVE-2023-41993?
How do I remediate CVE-2023-41993?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-41993
Is Your Infrastructure Affected by CVE-2023-41993?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.