How severe is CVE-2023-4218?

CVE-2023-4218 has a CVSS score of 5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-4218?

CVE-2023-4218 affects the following packages: org.eclipse.platform:org.eclipse.core.runtime (Maven), org.eclipse.platform:org.eclipse.platform (Maven), org.eclipse.platform:org.eclipse.jface (Maven), org.eclipse.platform:org.eclipse.ui.forms (Maven), org.eclipse.platform:org.eclipse.ui.ide (Maven), org.eclipse.platform:org.eclipse.ui.workbench (Maven), org.eclipse.platform:org.eclipse.urischeme (Maven), org.eclipse.jdt:org.eclipse.jdt.ui (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-4218?

Update org.eclipse.platform:org.eclipse.core.runtime to 3.29.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-4218 is resolved across your whole dependency graph.

How do I detect CVE-2023-4218 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.platform:org.eclipse.core.runtime. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2023-4218 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2023-4218?

O3 pinpoints whether CVE-2023-4218 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2023-4218 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-4218, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-4218?

CVE-2023-4218 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-4218?

CVE-2023-4218 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-4218 published, and has it been updated?

CVE-2023-4218 was published on November 9, 2023 and was last updated on April 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2023-4218

MEDIUM

Eclipse IDE XXE in eclipse.platform

Also known asGHSA-j24h-xcpc-9jw8

Published

Nov 9, 2023

Updated

Apr 12, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk30th percentile+0.36%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

8 pkgs affected

☕org.eclipse.platform:org.eclipse.core.runtime☕org.eclipse.platform:org.eclipse.platform☕org.eclipse.platform:org.eclipse.jface☕org.eclipse.platform:org.eclipse.ui.forms☕org.eclipse.platform:org.eclipse.ui.ide☕org.eclipse.platform:org.eclipse.ui.workbench☕org.eclipse.platform:org.eclipse.urischeme☕org.eclipse.jdt:org.eclipse.jdt.ui

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In Eclipse IDE versions < 2023-09 (4.29) some files with xml content are parsed vulnerable against all sorts of XXE attacks. The user just needs to open any evil project or update an open project with a vulnerable file (for example for review a foreign repository or patch).

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.platform:org.eclipse.core.runtime`	all versions	3.29.0
☕Maven	`org.eclipse.platform:org.eclipse.platform`	all versions	4.29.0
☕Maven	`org.eclipse.platform:org.eclipse.jface`	all versions	3.31.0
☕Maven	`org.eclipse.platform:org.eclipse.ui.forms`	all versions	3.13.0
☕Maven	`org.eclipse.platform:org.eclipse.ui.ide`	all versions	3.21.100
☕Maven	`org.eclipse.platform:org.eclipse.ui.workbench`	all versions	3.130.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Eclipse IDE versions < 2023-09 (4.29) some files with xml content are…

gitlab.eclipse.orgNVDNov 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.platform:org.eclipse.core.runtime. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.eclipse.platform:org.eclipse.core.runtime to 3.29.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-4218 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2023-4218 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-4218. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-4218 in your dependencies?

O3 detects CVE-2023-4218 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works