dbcve.org
CamelApplication · Apache

CVE-2026-40048

HIGH · 7.8 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to 4.18.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Camel-PQC FileBasedKeyLifecycleManager class deserializes the contents of `<keyId>.key` files in the configured key directory using java.io.ObjectInputStream without applying any ObjectInputFilter or class-loading restrictions. The cast to `java.security.KeyPair` is evaluated only after `readObject()` has already returned, so any `readObject()` side effects in the deserialized object run before the type check. An attacker who can write to the key directory used by a Camel application — for example through a path traversal into the directory, misconfigured filesystem permissions on the volume where keys are stored, a compromised key provisioning pipeline, or a symlink attack — can place a crafted serialized Java object that, when deserialized during normal key lifecycle operations, results in arbitrary code execution in the context of the application. This issue affects Apache Camel: from 4.19.0 before 4.20.0, from 4.18.0 before 4.18.2. Users are recommended to upgrade to version 4.20.0, which fixes the issue by replacing java.io.ObjectInputStream-based key and metadata storage with standard PKCS#8 (private key) / X.509 SubjectPublicKeyInfo (public key) Base64 JSON encoding. For users on the 4.18.x LTS releases stream, upgrade to 4.18.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Camel's FileBasedKeyLifecycleManager deserializes Java key files using ObjectInputStream without any filter, allowing attackers who can write to the key directory to inject malicious serialized objects that execute arbitrary code during deserialization before the type check completes.

MitigationUpgrade Apache Camel to version 4.20.0 (or 4.18.2 for LTS) to replace unsafe ObjectInputStream deserialization with standard PKCS#8/X.509 encoding; also audit key directory permissions to prevent unauthorized write access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 4.18.0, < 4.18.2= 4.19.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Apache Camel version
    Run 'mvn dependency:tree' or check your dependency management to find the camel-core version. Also check pom.xml or build.gradle for the Camel version. On running systems, check the logs for 'Apache Camel' startup messages which display the version.
    Affected if Version is 4.18.0 through 4.18.1 (inclusive), or exactly 4.19.0
  2. Identify FileBasedKeyLifecycleManager usage
    Search your codebase and configuration files for 'FileBasedKeyLifecycleManager' class references. Check XML, YAML, or Java configuration where security keys are managed. Review any route definitions or camel-context XML files for key management components.
    Affected if FileBasedKeyLifecycleManager is configured or referenced in your Camel application
  3. Verify key directory location and permissions
    Locate the key directory used by FileBasedKeyLifecycleManager (check your configuration for the key directory path). On Linux/Unix, run 'ls -la <key_directory_path>' to check permissions. On Windows, right-click the folder, go to Properties > Security to view write permissions.
    Affected if The key directory exists and is writable by users other than the intended system account (especially by untrusted users or services)
  4. Check for Java deserialization filters
    Search for 'ObjectInputFilter' or 'ObjectInputStream' usage in the Camel-related code. Check JVM arguments for '-Djdk.serialFilter=' settings. Review any custom ObjectInputStream implementations in your key management code.
    Affected if No deserialization filter is configured, or the existing filter allows arbitrary classes (not restricted to expected KeyPair types)

Your environment is affected if you run a vulnerable Camel version (4.18.0-4.18.1 or 4.19.0), use FileBasedKeyLifecycleManager, and the key directory is writable by an attacker who could inject malicious serialized objects.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.18.2 or later
Fixed in 4.18.2
Interim mitigation

Upgrade Apache Camel to version 4.20.0 (or 4.18.2 for LTS) to replace unsafe ObjectInputStream deserialization with standard PKCS#8/X.509 encoding; also audit key directory permissions to prevent unauthorized write access.

Recommended fix High confidence

Camel 4.18.2 (for 4.18.x users) or Camel 4.20.0 (for 4.19.x users)

  1. 1. Identify the Camel version currently in use by checking your project dependencies (Maven pom.xml, Gradle build.gradle, or application libraries)
  2. 2. If using Camel 4.18.0 or 4.18.1, plan upgrade to version 4.18.2
  3. 3. If using Camel 4.19.0, plan upgrade to version 4.20.0
  4. 4. Before upgrading, review the Camel 4.20.0 release notes for any breaking changes compared to your current version
  5. 5. Update your dependency version in your build configuration (e.g., change org.apache.camel:camel-dependencies version to 4.18.2 or 4.20.0)
  6. 6. Rebuild and test your application to ensure compatibility with the new version
  7. 7. Verify the fix: the vulnerability is resolved in 4.18.2 and 4.20.0 by replacing ObjectInputStream-based serialization with PKCS#8/X.509 standard formats
Caveat Review Camel 4.20.0 release notes; major version upgrades in Camel may include breaking API changes, especially when migrating from 4.19.x to 4.20.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40048 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40048 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data