PoC Monitor
← All CVEs
CVE-2026-55993published 6 Jul 2026 08:13 UTCData: JSON · API

Apache Software Foundation Apache Camel Atmosphere Websocket

Apache Camel Atmosphere Websocket: The inbound consumer maps externally-supplied WebSocket query parameters into the Exchange without a HeaderFilterStrategy, allowing injection of Camel control headers - enabling influencing internal behaviour

Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Atmosphere Websocket Component. The camel-atmosphere-websocket consumer mapped inbound WebSocket query parameters into the Camel Exchange header map without applying any HeaderFilterStrategy (WebsocketConsumer.sendEventNotification() iterates the query-string map collected in WebsocketConsumer.service() and copies each entry into the Exchange). Because nothing blocked the Camel header namespace, a client connecting to the WebSocket endpoint could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTP_URI) - simply by supplying them as query parameters. In a route where the WebSocket consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values and sent to the attacker, disclosing environment variables, application properties and vault secrets. When the WebSocket endpoint is exposed without authentication, this is reachable by an unauthenticated remote attacker. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.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.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes the consumer apply the HeaderFilterStrategy it already inherits from the HTTP/servlet stack, filtering the Camel header namespace case-insensitively on inbound mapping, so externally-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from the inbound message before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), require authentication on the WebSocket endpoint, and avoid bridging an untrusted consumer directly into an HTTP producer whose target URI can be driven from message headers.

First public PoC 16 daysafter publication · 22 Jul 2026
Public PoCs11 on GitHub
CVSS7.5high · scored by CISA ADP · CWE-20
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 Atmosphere Websocket
  • >= 4.0.0, < 4.14.8
  • >= 4.15.0, < 4.18.3
  • >= 4.19.0, < 4.21.0

Fixed in 4.14.8, 4.18.3, 4.21.0

Mitigation

Upgrade Apache Camel Atmosphere Websocket to 4.14.8 or 4.18.3 or 4.21.0 or later.

References

Timeline

Days relative to CVE publication
-3t=0+3+6+9+12+15+18CVE published6 Jul 2026 · t = 0First public PoC22 Jul 2026 · t+16d

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

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
oscerd/CVE-2026-55993 22 Jul 2026 +16 d 0 PoC

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-55993
Evidence
oscerd/CVE-2026-55993/README.md:103

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-55993 Apache Software Foundation Apache Camel Atmosphere Websocket exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/exploit/attack"; reference:url,poc.griffinguard.io/cve/CVE-2026-55993; classtype:web-application-attack; sid:9828845; rev:1;)

Sigma

Template generated from PoC characteristics. Review before deploying.

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