oscerd/cve-2026-46457Reproducer for CVE-2026-46457 — Apache Camel camel-nats inbound header injection (Camel control-header injection via a NATS publisher; CamelHttpUri -> SSRF)
Runnable proof-of-concept reproducers for the same Apache Camel vulnerability, one per runtime:
| Runtime | Directory | Stack |
|---|---|---|
| Camel Spring Boot | camel-spring-boot/ | Spring Boot 3.2.0 + camel-spring-boot 4.18.2 |
| Camel Quarkus | camel-quarkus/ | Quarkus 3.36.0 + Camel Quarkus 3.36.0 (bundles Camel 4.20.0) |
Both are affected versions (fixed in 4.14.8 / 4.18.3 / 4.21.0), and both demonstrate the identical defect:
NatsConfiguration defaults headerFilterStrategy to a bare new DefaultHeaderFilterStrategy() with no
inbound rules, so NatsConsumer copies every inbound NATS message header onto the Exchange — including
CamelHttpUri. The camel-http producer honours that header as its request URI, so anyone who can publish to the
consumed subject redirects the outbound request to a target of their choosing (SSRF, CWE-20). The same technique
reaches any header-controlled producer (CamelFileName, CamelSqlQuery, ...).
Each subdirectory is a self-contained project (plus a NATS broker started by its docker-compose.yml) with its
own Dockerfile and README. In short, for either:
cd camel-spring-boot # or: cd camel-quarkus
mvn clean package
docker compose up -d --build
curl -s http://localhost:8080/exploit/attack
docker compose down
| Property | Value |
|---|---|
| Component | camel-nats |
| Affected Class | org.apache.camel.component.nats.NatsConfiguration (default DefaultHeaderFilterStrategy) / NatsConsumer |
| CWE | CWE-20: Improper Input Validation |
| Impact | A subject publisher injects Camel control headers → steer downstream producers (SSRF shown here) |
| Affected Versions | From 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0 |
| Fixed Versions | 4.14.8, 4.18.3, 4.21.0 |
| JIRA | CAMEL-23515 |
Advisory: https://camel.apache.org/security/CVE-2026-46457.html
These reproducers are provided for security research and authorized testing only, for a publicly disclosed and fixed vulnerability. Do not use them against systems without explicit permission.