Security readout for executives and security teams
Plain-English summary
This flaw can let someone who can write to an Infinispan cache make an Apache Camel application run malicious Java objects when it later reads aggregation data. It is serious because successful exploitation means code execution inside the affected application, but the attacker first needs cache write access.
Executive priority
Prioritize remediation for systems where Infinispan cache write access crosses team, service, or tenant boundaries. Treat internet-adjacent or broadly writable cache environments as urgent because impact is full application compromise.
Technical view
Apache Camel camel-infinispan remote aggregation repository uses java.io.ObjectInputStream on cache data without ObjectInputFilter. In affected 4.x ranges, crafted serialized data written to the relevant Infinispan cache may execute code during normal repository operations such as get or recover.
Likely exposure
Exposure is most likely in Camel applications using org.apache.camel:camel-infinispan with a ProtoStream-based remote aggregation repository backed by remote Infinispan. Affected ranges are 4.0.0 before 4.14.7, 4.15.0 before 4.18.2, and 4.19.0 before 4.20.0.
Exploitation context
The provided sources do not report active exploitation or KEV listing. Exploitation requires an attacker able to write to the Infinispan cache used by the Camel application, then wait for normal aggregation repository reads.
Researcher notes
This is CWE-502 unsafe deserialization. The issue follows the same vulnerability class as prior Camel deserialization CVEs cited by Apache. Evidence supports arbitrary code execution only when cache-write capability exists; no source in the bundle confirms public exploitation.
Mitigation direction
- Upgrade Apache Camel to 4.20.0 where possible.
- Use 4.14.7 for the 4.14.x LTS stream.
- Use 4.18.2 for the 4.18.x stream.
- Restrict write access to affected Infinispan caches to trusted services only.
- Check Red Hat errata for downstream package guidance.
Validation and detection
- Inventory applications depending on org.apache.camel:camel-infinispan.
- Confirm deployed Camel versions are outside the affected ranges.
- Identify use of remote aggregation repositories backed by Infinispan.
- Review who or what can write to the relevant Infinispan cache.
- Verify remediation through dependency manifests and runtime deployment versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-40858 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADPCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-27T10:01:35.538Z: Reported to Red Hat.
- 2026-04-27T09:38:55.466Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://camel.apache.org/security/CVE-2026-40858.htmlCVE reference, apache · vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-40858CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2463179CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40858.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:22453CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:17668CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.