How severe is CVE-2014-0002?

No CVSS score has been assigned to CVE-2014-0002 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-0002?

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

How do I fix CVE-2014-0002?

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

How do I detect CVE-2014-0002 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-2014-0002 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-2014-0002 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-0002, 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-2014-0002?

CVE-2014-0002 has an EPSS (Exploit Prediction Scoring System) score of 27.4%, placing it in the 98th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2014-0002?

CVE-2014-0002 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0002 published, and has it been updated?

CVE-2014-0002 was published on October 16, 2018 and was last updated on December 6, 2024. 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

CVE-2014-0002 — camel-core

Fix: apache/camel@2ec54fa

CVE-2014-0002 is a CWE-264 vulnerability in org.apache.camel:camel-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.camel:camel-core — see the affected versions and patch details below.

Apache Camel's XSLT component allows remote attackers to read arbitrary files

Published

Oct 16, 2018

Updated

Dec 6, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

27.4%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

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

The XSLT component in Apache Camel before 2.11.4 and 2.12.x before 2.12.3 allows remote attackers to read arbitrary files and possibly have other unspecified impact via an XML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.camel:camel-core`	all versions	2.11.4`org.apache.camel:camel-core:2.11.4`
☕Maven	`org.apache.camel:camel-core`	≥ 2.12.0&&< 2.12.3	2.12.3`org.apache.camel:camel-core:2.12.3`

Affected Products

1 product · 31 configurations

Application

camelapache

≤ 2.11.3

27 versions

1.0.01.1.01.2.01.3.01.4.01.5.01.6.01.6.11.6.21.6.31.6.42.0.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.

The XSLT component in Apache Camel before 2.11.4 and 2.12.x before 2.12.…

camel.apache.orgNVDMay 2020

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.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0002 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Fuse ESB Enterprise 7.1.0	see advisory	RHSA-2014:0452
Red Hat JBoss A-MQ 6.0	see advisory	RHSA-2014:0323
Red Hat JBoss BPMS 6.0	`camel`	RHSA-2014:0371
Red Hat JBoss BRMS 6.0	`camel`	RHSA-2014:0372
Red Hat JBoss Fuse Service Works 6.0	`camel`	RHSA-2014:0459

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0002 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works