CVE-2016-8749

Exploitation likely. EPSS gives it a 11% chance of exploitation in the next 30 days. Fixed in 2.16.5.

CVSS 3.09.8Critical EPSS percentile96th11% chance in 30 days CISA KEVNot listedNo confirmed exploitation
No public exploit known Fix2.16.5Upgrade to this build

Published 2017-03-28Updated 2026-05-13Sources: CVE.org, NVD, GitHub

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

Apache Software Foundation Apache CamelAffected: 2.16.0 to 2.16.4Upgrade to: not statedAffected: 2.17.0 to 2.17.4Upgrade to: not statedAffected: 2.18.0 to 2.18.1Upgrade to: not statedAffected: The unsupported Camel 2.x (2.14 and earlier) versions may be also affected.Upgrade to: not statedStated by: CVE record
Maven org.apache.camel:camel-jacksonAffected: < 2.16.5Upgrade to: 2.16.5Stated by: GitHub advisory

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record

Check whether your Apache Camel application includes the org.apache.camel:camel-jackson dependency and identify its version.
Update the dependency to the fixed release for your branch: 2.16.5, 2.17.5, or 2.18.2 (or later).
Test data-import and integration workflows after updating, then deploy the updated application.
Review application logs for unusual requests or unexpected application behavior while the update is pending.

Vendor advisory Usually a quick update

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Apache Camel's Jackson and JacksonXML unmarshalling operation are vulnerable to Remote Code Execution attacks.

In plain language

Written by AI from the record

Apache Camel installations using its Jackson data-reading component need an update because a malicious request can take over the application.

CVE-2016-8749 is a critical remote code execution flaw in Apache Camel Jackson and JacksonXML unmarshalling, caused by unsafe deserialization of attacker-controlled data.

If you're affected

Full application takeover
Business data exposure
Service disruption
Ransomware risk

What is it

Apache Camel can turn incoming data into software objects for an application to use. In affected setups, specially crafted data can act like a forged master key: instead of simply being read, it can give an attacker control of the application.

Who is affected

This matters to you if you run Apache Camel and your application uses its Jackson or JacksonXML data-reading capability. It is especially relevant for integrations that accept data from outside systems, partners, customers, or internet-facing services.

How urgent is it

An attacker can use crafted data to take control of an affected application remotely, so this deserves prompt scheduled remediation. It is not listed in CISA's catalog of vulnerabilities known to be exploited, and no public exploit code is on record; treat it as an amber priority and complete the update soon.

What to do — in detail

Confirm exposure by reviewing the deployed application's Maven dependency tree, packaged JARs, or software inventory for org.apache.camel:camel-jackson; also identify whether Jackson or JacksonXML unmarshalling is configured in Camel routes.

Upgrade to the fixed release for the maintained branch in use: 2.16.5, 2.17.5, or 2.18.2, or a later compatible release. Build and test the application after the dependency update, particularly routes that consume JSON or XML, because integration behavior and dependency compatibility should be validated before production deployment.

If patching is delayed, temporarily restrict untrusted sources from reaching routes that perform Jackson or JacksonXML unmarshalling, and require trusted upstream validation for data sent to those routes. Monitor application and integration logs for unexpected payloads, errors during unmarshalling, unusual child processes, or unexplained configuration changes. CISA has not assigned a KEV remediation due date because this CVE is not listed in KEV.

Technical context

Severity is CVSS 9.8 (Critical): AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The weakness is CWE-502, unsafe deserialization, affecting Apache Camel Jackson and JacksonXML unmarshalling and enabling remote code execution with crafted serialized input. CISA KEV does not list this CVE, and no public exploit code is on record. EPSS predicts a 9.9% likelihood of exploitation (95th percentile) with a flat trend; this is predictive rather than confirmation of in-the-wild exploitation. Press attention is rising.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

11% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

24 events over 3466 days, from the signal feeds we watch.

2026-09-23EPSS band changelow → moderateepss band change
2026-09-21EPSS band changemoderate → lowepss band change
2026-09-06EPSS band change0 → moderateepss band change
2026-09-05EPSS band changemoderate → 0epss band change
2026-08-31EPSS band change0 → moderateepss band change
2026-08-29EPSS band changemoderate → low

Affected products

Apache Software Foundationoss-project · USaka apache foundation
- Apache CamelDev ToolOn-premDevTools & CI / build-test-tools
Mavenpackage-ecosystem
- org.apache.camel:camel-jacksonOSS Libraries
apacheoss-project · USaka apache http server, apache httpd
- camelLibraryLibraryOSS Libraries / generic-library

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 9.8 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity HighTotal loss of integrity — attacker can modify any data in the component
Availability HighTotal denial of service — the component is completely unavailable