CamelApplication · Apache
CVE-2026-40858
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 · uneditedThe camel-infinispan component's ProtoStream-based remote aggregation repository deserializes data read from a remote Infinispan cache using java.io.ObjectInputStream without applying any ObjectInputFilter. An attacker who can write to the Infinispan cache used by a Camel application can inject a crafted serialized Java object that, when read during normal aggregation repository operations such as get or recover, results in arbitrary code execution in the context of the application. This issue affects Apache Camel: from 4.0.0 before 4.14.7, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0. Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.7. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2. The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23322 refers to the various commits that resolved the issue, and have more details. This issue follows the same class of vulnerability previously addressed in CVE-2024-22369, CVE-2024-23114 and CVE-2026-25747.
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 confidenceThe camel-infinispan component deserializes data from remote Infinispan caches using java.io.ObjectInputStream without applying an ObjectInputFilter, allowing an attacker who can write to the cache to inject malicious serialized Java objects that execute arbitrary code during aggregation operations like get or recover.
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
>= 4.0.0, < 4.14.7>= 4.15.0, < 4.18.2= 4.19.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Camel versionCheck the Camel version in your application (via pom.xml, manifest, or runtime diagnostic). Compare it against the affected ranges: >= 4.0.0 and < 4.14.7, or >= 4.15.0 and < 4.18.2, or exactly 4.19.0.Affected if Your Camel version falls within any of these affected ranges.
-
Verify camel-infinispan component is presentInspect your application's dependencies or deployed modules for the camel-infinispan component. Check build files (pom.xml, gradle) or the runtime classpath for this artifact.Affected if The camel-infinispan component is included in your deployment.
-
Confirm ProtoStream aggregation repository is configuredSearch configuration files, Spring XML, YAML, or Java code for aggregation repository definitions that reference Infinispan with ProtoStream serialization. Look for beans or route configurations using InfinispanRemoteAggregationRepository or similar repository classes.Affected if Your application configures a remote Infinispan-based aggregation repository using ProtoStream serialization.
-
Identify get and recover operations in useReview your Camel routes and code that invoke the aggregation repository. Look for calls that perform get or recover operations on the Infinispan aggregation repository.Affected if Your routes or code invoke get or recover methods on the vulnerable aggregation repository.
You are affected if you run a vulnerable Apache Camel version with the camel-infinispan component deployed and a ProtoStream-based remote aggregation repository configured, where get or recover operations are performed on it.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.14.74.18.2
Upgrade Apache Camel to version 4.20.0 (or 4.14.7 for LTS 4.14.x, or 4.18.2 for 4.18.x) to apply the fix that adds proper ObjectInputFilter configuration.
4.20.0 (or 4.14.7 for 4.14.x LTS stream, or 4.18.2 for 4.18.x stream)
- Identify the current Apache Camel version in use by checking the project's dependency management (e.g., pom.xml, build.gradle, or application manifests)
- Determine which upgrade path applies based on current version: if on 4.14.x stream, target 4.14.7; if on 4.18.x stream, target 4.18.2; otherwise target 4.20.0
- Update the Camel version in the project's dependency management file to the target version
- Rebuild and test the application to ensure compatibility with the new version
- Redeploy the application with the upgraded Camel version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Camel
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40858 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40858 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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