Skip to content
Fencer Intel
medium 5.0

CVE-2015-0263 json

Apache Camel XML External Entity vulnerability

published 2015-06-03 11 y ago modified 2026-06-17 4 mo ago also GHSA-3hrc-f439-727g , EUVD-2018-0487

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.5%
EPSS 7.5% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

XML external entity (XXE) vulnerability in the XML converter setup in converter/jaxp/XmlConverter.java in Apache Camel before 2.13.4 and 2.14.x before 2.14.2 allows remote attackers to read arbitrary files via an external entity in an SAXSource.

Patch / fix

  • maven org.apache.camel:camel-core 2.13.4, 2.14.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-0263 updated cvss 5.0

Camel: XXE in via SAXSource expansion

  • Red Hat OpenShift Enterprise 1 camel
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Enterprise 2 camel
    affected: no fix available
  • Red Hat JBoss A-MQ 6.1
    fixed: vendor fix RHSA-2015:1041
  • Red Hat JBoss BPMS 6.0
    fixed: vendor fix RHSA-2015:1539
  • Red Hat JBoss BRMS 6.0
    fixed: vendor fix RHSA-2015:1538
  • Red Hat JBoss Fuse 6.1
    fixed: vendor fix RHSA-2015:1041
  • Red Hat JBoss Fuse Service Works 6.2
    fixed: vendor fix RHSA-2015:2558

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

7.47% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel-core
<2.13.4
>=2.14.0, <2.14.2
2.13.4
2.14.2

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.