Skip to content
Fencer Intel
high 7.5

CVE-2020-11994 json

Server side template injection in Apache Camel

published 6y ago modified 4mo ago also GHSA-9vfj-5g7h-4p24 , EUVD-2020-0549

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

Summary

Server-Side Template Injection and arbitrary file disclosure on Camel templating components

Patch / fix

  • maven org.apache.camel:camel-robotframework 3.4.0

Is CVE-2020-11994 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2020-11994 updated cvss 7.5

camel: server-side template injection and arbitrary file disclosure on templating components

  • Red Hat BPM Suite 6 camel Red Hat JBoss A-MQ 6 camel Red Hat JBoss Fuse Service Works 6 camel
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 6.3
    fixed: vendor fix RHSA-2020:3587
  • Red Hat Fuse 7.8.0
    fixed: vendor fix RHSA-2020:5568

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

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

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel-robotframework
<3.4.0
3.4.0

Affected products

  • n/a Apache Camel

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

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.