What is CVE-2026-25747?

CVE-2026-25747 is a high-severity insecure deserialization vulnerability in org.apache.camel:camel-leveldb (maven), affecting versions >= 3.0.0, < 4.10.9. It is fixed in 4.10.9, 4.14.5, 4.18.0. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

Which versions of org.apache.camel:camel-leveldb are affected by CVE-2026-25747?

org.apache.camel:camel-leveldb (maven) versions >= 3.0.0, < 4.10.9 is affected.

Is there a fix for CVE-2026-25747?

Yes. CVE-2026-25747 is fixed in 4.10.9, 4.14.5, 4.18.0. Upgrade to this version or later.

Is CVE-2026-25747 exploitable, and should I be worried?

Whether CVE-2026-25747 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-25747 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-25747 in org.apache.camel:camel-leveldb

Q: Which versions of org.apache.camel:camel-leveldb are affected by CVE-2026-25747?

org.apache.camel:camel-leveldb (maven) versions >= 3.0.0, < 4.10.9 is affected.

Q: Is there a fix for CVE-2026-25747?

Yes. CVE-2026-25747 is fixed in 4.10.9, 4.14.5, 4.18.0. Upgrade to this version or later.

Q: Is CVE-2026-25747 exploitable, and should I be worried?

Whether CVE-2026-25747 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-25747 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-25747?

Upgrade: org.apache.camel:camel-leveldb to 4.10.9 or later, org.apache.camel:camel-leveldb to 4.14.5 or later, org.apache.camel:camel-leveldb to 4.18.0 or later.

Summary

Apache Camel Deserializes Untrusted Data in its LevelDB Component

Deserialization of Untrusted Data vulnerability in Apache Camel LevelDB component.

The Camel-LevelDB DefaultLevelDBSerializer class deserializes data read from the LevelDB aggregation repository using java.io.ObjectInputStream without applying any ObjectInputFilter or class-loading restrictions. An attacker who can write to the LevelDB database files used by a Camel application can inject a crafted serialized Java object that, when deserialized during normal aggregation repository operations, results in arbitrary code execution in the context of the application.
This issue affects Apache Camel: from 4.10.0 before 4.10.8, from 4.14.0 before 4.14.5, from 4.15.0 before 4.18.0.

Users are recommended to upgrade to version 4.18.0, which fixes the issue. For the 4.10.x LTS releases, users are recommended to upgrade to 4.10.9, while for 4.14.x LTS releases, users are recommended to upgrade to 4.14.5

Impact

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

Affected versions

org.apache.camel:camel-leveldb (>= 3.0.0, < 4.10.9) org.apache.camel:camel-leveldb (>= 4.11.0, < 4.14.5) org.apache.camel:camel-leveldb (>= 4.15.0, < 4.18.0)

Security releases

org.apache.camel:camel-leveldb → 4.10.9 (maven) org.apache.camel:camel-leveldb → 4.14.5 (maven) org.apache.camel:camel-leveldb → 4.18.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.camel:camel-leveldb to 4.10.9 or later; org.apache.camel:camel-leveldb to 4.14.5 or later; org.apache.camel:camel-leveldb to 4.18.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-25747? CVE-2026-25747 is a high-severity insecure deserialization vulnerability in org.apache.camel:camel-leveldb (maven), affecting versions >= 3.0.0, < 4.10.9. It is fixed in 4.10.9, 4.14.5, 4.18.0. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
Which versions of org.apache.camel:camel-leveldb are affected by CVE-2026-25747? org.apache.camel:camel-leveldb (maven) versions >= 3.0.0, < 4.10.9 is affected.
Is there a fix for CVE-2026-25747? Yes. CVE-2026-25747 is fixed in 4.10.9, 4.14.5, 4.18.0. Upgrade to this version or later.
Is CVE-2026-25747 exploitable, and should I be worried? Whether CVE-2026-25747 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-25747 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-25747?
- Upgrade org.apache.camel:camel-leveldb to 4.10.9 or later
- Upgrade org.apache.camel:camel-leveldb to 4.14.5 or later
- Upgrade org.apache.camel:camel-leveldb to 4.18.0 or later