PoC Monitor
← All CVEs
CVE-2026-40860published 27 Apr 2026 08:03 UTCData: JSON · API

Apache Software Foundation Apache Camel

Apache Camel: Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp

JmsBinding.extractBodyFromJms() in camel-jms, and the equivalent JmsBinding class in camel-sjms, deserialized the payload of incoming JMS ObjectMessage values via javax.jms.ObjectMessage.getObject() without applying any ObjectInputFilter, class allowlist or class denylist. Because this code path is reached whenever the mapJmsMessage option is enabled (the default) and Camel acts as a JMS consumer, an attacker able to publish a crafted ObjectMessage to a queue or topic consumed by a Camel application could achieve remote code execution when a deserialization gadget chain was present on the classpath. The same handling was reached transitively through camel-sjms2 (whose Sjms2Endpoint extends SjmsEndpoint) and through camel-amqp (whose AMQPJmsBinding extends JmsBinding), and by other JMS-family components built on JmsComponent such as camel-activemq and camel-activemq6. This issue affects Apache Camel: from 3.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.

First public PoC 74 daysafter publication · 10 Jul 2026
Public PoCs11 on GitHub
CVSS9.8critical · scored by CISA ADP · CWE-502
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Apache Software Foundation Apache Camel
  • >= 3.0.0, < 4.14.7
  • >= 4.15.0, < 4.18.2
  • >= 4.19.0, < 4.20.0

Fixed in 4.14.7, 4.18.2, 4.20.0

Mitigation

Upgrade Apache Camel to 4.14.7 or 4.18.2 or 4.20.0 or later.

References

Timeline

Days relative to CVE publication
t=0+14+28+42+56+70CVE published27 Apr 2026 · t = 0First public PoC10 Jul 2026 · t+74d

First public PoC 74 days after publication; not in CISA KEV. First PoC: oscerd/CVE-2026-40860 (created 10 Jul 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs · 1 not a PoC

PoCs 1
RepositoryCreatedStarsAssessment
oscerd/CVE-2026-40860 10 Jul 2026 +74 d 0 PoC
Not a PoC 1
RepositoryCreatedStarsAssessment
oscerd/CVE-2026-43866 12 Jul 2026 +76 d 0 Not a PoC · unrelated

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

PoC characteristics

What to hunt for in your logs · from 1 PoC repo

GET /exploit/attack

Ports
8080
Seen in
1 repo: oscerd/CVE-2026-40860
Evidence
oscerd/CVE-2026-40860/README.md:114

Regex

Generated from PoC characteristics; not yet reviewed. Matches the request path and query.

GET /exploit/attack
(?i)^/exploit/attack(?:[?#].*)?$

Suricata

Template generated from PoC characteristics. Review before deploying.

GET /exploit/attack
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-40860 Apache Software Foundation Apache Camel exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/exploit/attack"; reference:url,poc.griffinguard.io/cve/CVE-2026-40860; classtype:web-application-attack; sid:9514858; rev:1;)

Sigma

Template generated from PoC characteristics. Review before deploying.

GET /exploit/attack
title: Apache Software Foundation Apache Camel exploit attempt (CVE-2026-40860)
id: gg-pocmon-cve-2026-40860-9514858
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-40860. Generated, not reviewed.
references:
  - https://poc.griffinguard.io/cve/CVE-2026-40860
logsource:
  category: webserver
detection:
  selection:
    cs-method: GET
    cs-uri-stem|contains|all:
      - '/exploit/attack'
  condition: selection
falsepositives:
  - Authorized vulnerability scanning
level: critical
tags:
  - attack.initial_access
  - attack.t1190
  - cve.2026.40860