How severe is CVE-2018-8027?

CVE-2018-8027 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-8027?

CVE-2018-8027 affects the following packages: org.apache.camel:camel-core (Maven), org.apache.camel:camel-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-8027?

Update org.apache.camel:camel-core to 2.20.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-8027 is resolved across your whole dependency graph.

How do I detect CVE-2018-8027 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-8027 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.

Is CVE-2018-8027 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-8027 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-8027?

CVE-2018-8027 has an EPSS (Exploit Prediction Scoring System) score of 5.4%, placing it in the 93th 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-2018-8027?

CVE-2018-8027 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-2018-8027 published, and has it been updated?

CVE-2018-8027 was published on July 31, 2018 and was last updated on October 24, 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

Not in CISA KEV

CRITICAL severity

CVE-2018-8027 — camel-core

CRITICALFix: apache/camel@ec3d0db

CVE-2018-8027 is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in org.apache.camel:camel-core. A fix is available for org.apache.camel:camel-core — see the affected versions and patch details below.

Apache is vulnerable to XXE in XSD validation processor

Also known asGHSA-8vfm-4388-6rpc

Published

Jul 31, 2018

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

5.4%probability of exploitation in next 30 days

Lower Risk-0.07%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.apache.camel:camel-core☕org.apache.camel:camel-core

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

Apache Camel 2.20.0 to 2.20.3 and 2.21.0 Core is vulnerable to XXE in XSD validation processor.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.camel:camel-core`	≥ 2.20.0&&< 2.20.4	2.20.4`org.apache.camel:camel-core:2.20.4`
☕Maven	`org.apache.camel:camel-core`	≥ 2.21.0&&< 2.21.1	2.21.1`org.apache.camel:camel-core:2.21.1`

Affected Products

1 product · 2 configurations

Application

camelapache

≥ 2.20.0 && ≤ 2.20.3

1 version

2.21.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-core to 2.20.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-8027 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.

Frequently Asked Questions

Apache Camel 2.20.0 to 2.20.3 and 2.21.0 Core is vulnerable to XXE in XSD validation processor.

O3 Security · Impact-Aware SCA

Is CVE-2018-8027 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works