Description
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.
Published: 2026-10-19
Score: 8.2 High
EPSS: n/a
KEV: No
Impact: Remote Server‑Side Request Forgery causing credential disclosure
Action: Immediate Patch
AI Analysis

Impact

Apache Camel’s AS2 component allows a remote AS2 sender to supply an arbitrary asynchronous Message Disposition Notification (MDN) delivery address. The component then uses that address verbatim, creating a server‑side request forgery that can reach internal hosts only accessible from the deployment. If the Camel AS2 receiver has credentials configured for MDN delivery, those credentials are sent to the attacker‑specified endpoint, resulting in credential disclosure. The CVSS score of 8.2 indicates high severity.

Affected Systems

The vulnerability affects Apache Camel versions from 4.0.0 up to and including 4.18.4, from 4.19.0 up to 4.21.x, and from 4.22.0 up to 4.22.0. Users on the 4.18.x LTS stream must upgrade to 4.18.5; those on the 4.22.x LTS stream to 4.22.1; and all users should move to Apache Camel 4.23.0 for the upstream fix.

Risk and Exploitability

With a CVSS score of 8.2 but no available EPSS value, the exploitation probability is not quantified; the vulnerability is not yet listed in CISA’s KEV catalog. The attack vector requires a partner to send an AS2 message with a crafted MDN URL. Successful exploitation allows the attacker to coerce the Camel server into connecting to arbitrary hosts, including internal systems, and to transmit credentials that the server holds for MDN delivery. While the attack is limited to AS2 receivers, its impact on confidentiality and integrity of internal services is substantial.

Generated by OpenCVE AI on October 19, 2026 at 11:40 UTC.

Remediation

Vendor Solution

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.


Vendor Workaround

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.


OpenCVE Recommended Actions

  • Apply the Apache Camel update to v4.23.0, or to v4.18.5 for the 4.18.x LTS stream, or to v4.22.1 for the 4.22.x LTS stream, as these releases contain the fix that constrains asynchronous MDN destinations.
  • For installations that cannot upgrade immediately, configure outbound connectivity restrictions so that the AS2 receiver can only contact legitimate partner endpoints for MDN delivery, and ensure that any credentials used for MDN delivery are scoped only to those partners.
  • Verify that the AS2 configuration does not allow externally supplied MDN addresses to be used without validation, and if possible enforce a whitelist of approved MDN endpoints in the Camel AS2 component settings.

Generated by OpenCVE AI on October 19, 2026 at 11:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache apache Camel
Apache camel
Vendors & Products Apache
Apache apache Camel
Apache camel

Mon, 19 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache Camel: Camel-AS2 Server-Side Request Forgery and Credential Disclosure via Asynchronous MDN Delivery Address
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N'}


Subscriptions

Apache Apache Camel Camel
cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-19T10:28:48.809Z

Reserved: 2026-08-26T09:43:30.068Z

Link: CVE-2026-80344

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-19T11:17:21.363

Modified: 2026-10-19T11:17:21.363

Link: CVE-2026-80344

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T16:30:13Z

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)