CVE-2026-80344: Apache Camel: Camel-AS2 Server-Side Request Forgery and Credential Disclosure via Asynchronous MDN Delivery Address
Server-Side Request Forgery (SSRF) vulnerability in Apache Camel AS2 component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
In the AS2 protocol the sender of a message may request that the Message Disposition Notification be returned asynchronously to an address the sender supplies. camel-as2 took that address from the inbound message and used it as the destination for the outgoing receipt without constraining it to anything the deployment had configured. A remote partner therefore chose the host the Camel instance would connect to when delivering the MDN. That gives server-side request forgery from the position of the AS2 receiver, including reaching hosts that are only routable from inside the deployment's network, and where the outbound connection carries credentials configured for MDN delivery those credentials are presented to the attacker-chosen destination.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The asynchronous MDN destination is now constrained rather than taken verbatim from the inbound message. For deployments that cannot upgrade immediately, restrict outbound connectivity from the AS2 receiver to the partner endpoints it legitimately delivers receipts to, and do not attach credentials to MDN delivery that are valid for any host other than those partners.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.23.0 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.18.5 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.22.1 - Compensating control
Restrict outbound connectivity from the AS2 receiver to the partner endpoints it legitimately delivers receipts to.
- Compensating control
Do not attach credentials to MDN delivery that are valid for any host other than the legitimate partner endpoints.
Event History
Frequently Asked Questions
Who can exploit this issue?
A remote AS2 message sender or partner that can submit an inbound AS2 message to a vulnerable Camel AS2 receiver can supply an asynchronous MDN delivery address. No authentication, user interaction, or special attack complexity is indicated by the provided severity vector.
What is the practical impact of a successful exploit?
The attacker can cause the Camel instance to make an outbound connection to a host they choose, including hosts reachable only from the deployment's internal network. If credentials are configured for MDN delivery, those credentials can be presented to the attacker-chosen destination.
Which releases are affected and what versions remediate the issue?
Affected releases are Apache Camel 4.0.0 through versions before 4.18.5, and 4.19.0 through versions before 4.22.1. Upgrade to 4.18.5 on the 4.18.x LTS stream, 4.22.1 on the 4.22.x LTS stream, or 4.23.0.
What configuration condition makes the vulnerability relevant?
The issue is relevant when the Camel AS2 component receives messages that request asynchronous MDN delivery. Vulnerable versions use the MDN destination supplied in the inbound message rather than constraining it to a deployment-configured destination.