How severe is GHSA-429q-mrc4-38fr?

No CVSS score has been assigned to GHSA-429q-mrc4-38fr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-429q-mrc4-38fr?

GHSA-429q-mrc4-38fr affects the following packages: org.apache.camel:camel-leveldb (Maven), org.apache.camel:camel-leveldb (Maven), org.apache.camel:camel-leveldb (Maven). Ecosystems affected: Maven.

How do I fix GHSA-429q-mrc4-38fr?

Update org.apache.camel:camel-leveldb to 4.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-429q-mrc4-38fr is resolved across your whole dependency graph.

How do I detect GHSA-429q-mrc4-38fr in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-leveldb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-429q-mrc4-38fr 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.

How does O3 Security protect against GHSA-429q-mrc4-38fr?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-429q-mrc4-38fr can be triaged on real exposure rather than presence alone.

Is GHSA-429q-mrc4-38fr actively exploited in the wild?

No public exploit code has been indexed for GHSA-429q-mrc4-38fr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-429q-mrc4-38fr?

GHSA-429q-mrc4-38fr has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 58th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-429q-mrc4-38fr?

GHSA-429q-mrc4-38fr is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-429q-mrc4-38fr published, and has it been updated?

GHSA-429q-mrc4-38fr was published on February 23, 2026 and was last updated on February 25, 2026. 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

GHSA-429q-mrc4-38fr — camel-leveldb

Fix: apache/camel@0e3ac39

GHSA-429q-mrc4-38fr is a Deserialization of Untrusted Data vulnerability in org.apache.camel:camel-leveldb. A fix is available for org.apache.camel:camel-leveldb — see the affected versions and patch details below.

Apache Camel Deserializes Untrusted Data in its LevelDB Component

Also known asCVE-2026-25747

Published

Feb 23, 2026

Updated

Feb 25, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-429q-mrc4-38fr.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

☕org.apache.camel:camel-leveldb☕org.apache.camel:camel-leveldb☕org.apache.camel:camel-leveldb

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

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.camel:camel-leveldb`	≥ 3.0.0&&< 4.10.9	4.10.9`org.apache.camel:camel-leveldb:4.10.9`
☕Maven	`org.apache.camel:camel-leveldb`	≥ 4.11.0&&< 4.14.5	4.14.5`org.apache.camel:camel-leveldb:4.14.5`
☕Maven	`org.apache.camel:camel-leveldb`	≥ 4.15.0&&< 4.18.0	4.18.0`org.apache.camel:camel-leveldb:4.18.0`

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-leveldb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-leveldb to 4.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-429q-mrc4-38fr 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-429q-mrc4-38fr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-429q-mrc4-38fr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 Came

O3 Security · Impact-Aware SCA

Is GHSA-429q-mrc4-38fr in your dependencies?

O3 Security finds GHSA-429q-mrc4-38fr across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works