CVE-2023-4357

HIGHNVD 8.88.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 46% probability of exploitation within the next 30 days (top 1.3% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 46%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Insufficient validation of untrusted input in XML in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to bypass file access restrictions via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
8.8
EG Score
8.9(high)
EG Risk
58(Track)
EG Risk 58/100SSVC: Track

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 computed
Severity89% × 45%
Exploitation46% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
46%
EPSS %ILE
99%
KEV
Not listed

Published

August 15, 2023

Last Modified

June 17, 2026

References (12)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (126 versions)116.0.5845.96-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 116.0.5845.96-1~deb11u1 (24 versions)116.0.5845.96-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium—116.0.5845.96-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium—116.0.5845.96-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 4× in last 7d / 33× 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.

  1. 2026-08-08 16:35 UTCEPSS rescore
  2. 2026-08-07 16:25 UTCEPSS rescore
  3. 2026-08-06 13:45 UTCEPSS rescore
  4. 2026-08-04 15:07 UTCEPSS rescore
  5. 2026-08-02 04:23 UTCOSV refresh
  6. 2026-07-30 16:26 UTCEPSS rescore
  7. 2026-07-30 16:26 UTCEPSS rescore
  8. 2026-07-30 01:28 UTCEPSS rescore
  9. 2026-07-28 15:34 UTCEPSS rescore
  10. 2026-07-28 15:34 UTCEPSS rescore
  11. 2026-07-26 14:52 UTCEPSS rescore
  12. 2026-07-25 14:16 UTCEPSS rescore
  13. 2026-07-24 14:16 UTCEPSS rescore
  14. 2026-07-24 14:16 UTCEPSS rescore
  15. 2026-07-23 14:16 UTCEPSS rescore
  16. 2026-07-23 02:26 UTCEG score recompute▲ 0.10
  17. 2026-07-22 23:13 UTCEG score recompute
  18. 2026-07-22 14:06 UTCEPSS rescore
  19. 2026-07-21 15:23 UTCEPSS rescore
  20. 2026-07-21 15:23 UTCEPSS rescore
  21. 2026-07-20 17:06 UTCEPSS rescore
  22. 2026-07-19 14:29 UTCEPSS rescore
  23. 2026-07-19 14:29 UTCEPSS rescore
  24. 2026-07-18 10:03 UTCEPSS rescore
  25. 2026-07-18 10:03 UTCEPSS rescore
Show 67 more
  1. 2026-07-16 17:01 UTCEPSS rescore
  2. 2026-07-15 16:56 UTCEPSS rescore
  3. 2026-07-15 16:56 UTCEPSS rescore
  4. 2026-07-15 12:19 UTCOSV refresh
  5. 2026-07-13 22:28 UTCEPSS rescore
  6. 2026-07-13 22:28 UTCEPSS rescore
  7. 2026-07-13 06:11 UTCEPSS rescore
  8. 2026-07-13 06:11 UTCEPSS rescore
  9. 2026-07-12 05:45 UTCEPSS rescore
  10. 2026-07-11 08:26 UTCEPSS rescore
  11. 2026-07-09 19:08 UTCEPSS rescore
  12. 2026-07-08 15:13 UTCEPSS rescore
  13. 2026-07-04 06:29 UTCEPSS rescore
  14. 2026-07-04 06:29 UTCEPSS rescore
  15. 2026-07-02 16:59 UTCEPSS rescore
  16. 2026-07-01 15:05 UTCEPSS rescore
  17. 2026-06-29 14:05 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-27 12:34 UTCOSV refresh
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-23 21:31 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
  26. 2026-06-22 14:24 UTCEPSS rescore
  27. 2026-06-22 14:24 UTCEPSS rescore
  28. 2026-06-21 01:58 UTCEPSS rescore
  29. 2026-06-21 01:58 UTCEPSS rescore
  30. 2026-06-19 19:24 UTCEPSS rescore
  31. 2026-06-19 19:24 UTCEPSS rescore
  32. 2026-06-18 17:51 UTCEPSS rescore
  33. 2026-06-17 17:51 UTCEPSS rescore
  34. 2026-06-16 17:51 UTCEPSS rescore
  35. 2026-06-16 17:51 UTCEPSS rescore
  36. 2026-06-15 17:47 UTCEPSS rescore
  37. 2026-06-14 23:16 UTCEPSS rescore
  38. 2026-06-13 22:59 UTCEPSS rescore
  39. 2026-06-13 22:59 UTCEPSS rescore
  40. 2026-06-12 23:11 UTCEPSS rescore
  41. 2026-06-12 23:10 UTCEPSS rescore
  42. 2026-06-11 13:59 UTCEPSS rescore
  43. 2026-06-10 22:17 UTCEPSS rescore
  44. 2026-06-10 13:21 UTCEPSS rescore
  45. 2026-06-09 23:17 UTCOSV refresh
  46. 2026-06-08 14:16 UTCEPSS rescore
  47. 2026-06-08 14:16 UTCEPSS rescore
  48. 2026-06-07 15:24 UTCEPSS rescore
  49. 2026-06-07 15:23 UTCEPSS rescore
  50. 2026-06-06 13:46 UTCEPSS rescore
  51. 2026-06-06 13:46 UTCEPSS rescore
  52. 2026-06-05 22:46 UTCEPSS rescore
  53. 2026-06-05 22:46 UTCEPSS rescore
  54. 2026-06-05 06:09 UTCEPSS rescore
  55. 2026-06-05 06:09 UTCEPSS rescore
  56. 2026-06-05 06:09 UTCEPSS rescore
  57. 2026-06-02 20:12 UTCEPSS rescore
  58. 2026-06-02 20:12 UTCEPSS rescore
  59. 2026-06-01 13:51 UTCEPSS rescore
  60. 2026-06-01 13:51 UTCEPSS rescore
  61. 2026-05-31 00:15 UTCEPSS rescore
  62. 2026-05-31 00:15 UTCEPSS rescore
  63. 2026-05-29 13:43 UTCEPSS rescore
  64. 2026-05-28 13:44 UTCEPSS rescore
  65. 2026-05-24 19:18 UTCEG score recompute
  66. 2026-05-24 19:18 UTCVendor advisory
  67. 2026-05-24 19:18 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 PoClon5948/CVE-2023-4357-Exploitation
    First seen Mar 17, 2024

    Network Security Project

    Open source ↗
  • GitHub PoCsunu11/chrome-CVE-2023-4357
    First seen Nov 29, 2023

    poc

    Open source ↗
  • GitHub PoCxcanwin/CVE-2023-4357-Chrome-XXE
    First seen Nov 17, 2023

    [漏洞复现] 全球首款单文件利用 CVE-2023-4357 Chrome XXE 漏洞 EXP, 实现对访客者本地文件窃取. Chrome XXE vulnerability EXP, allowing attackers to obtain local files of visitors.

    Open source ↗

Frequently asked(5)

What is CVE-2023-4357?
CVE-2023-4357 is a high vulnerability published on August 15, 2023. Insufficient validation of untrusted input in XML in Google Chrome prior to 116.0.5845.96 allowed a remote attacker to bypass file access restrictions via a crafted HTML page. (Chromium security severity: Medium)
When was CVE-2023-4357 disclosed?
CVE-2023-4357 was first published in the National Vulnerability Database on August 15, 2023, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-4357 actively exploited?
CVE-2023-4357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46% probability of exploitation in the next 30 days, which ranks it in the top 1.3% of all scored CVEs.
What is the CVSS score of CVE-2023-4357?
CVE-2023-4357 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2023-4357?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-4357, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-4357

Explore →

Is Your Infrastructure Affected by CVE-2023-4357?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs