---
id: "CVE-2026-80344"
kind: "vulnerability"
aliases: ["CVE-2026-80344"]
title: "Apache Camel AS2: remote partner can make server connect to any host"
severity: "high"
cvss: 8.2
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "camel-as2", "edi-integration", "java", "package"]
not_affected_if: ["camel-as2-not-used", "fixed-version"]
published_at: "2026-10-19T11:17:21+00:00"
first_seen_at: "2026-10-23T21:57:17+00:00"
updated_at: "2026-10-25T03:04:22+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80344", "first_seen_at": "2026-10-23T21:57:17+00:00"}]
---

# Apache Camel AS2: remote partner can make server connect to any host

The camel-as2 component used a sender-supplied address from an AS2 message as the destination for the asynchronous Message Disposition Notification, without restriction. A remote AS2 partner can therefore make the Camel instance send requests to hosts it chooses, including internal hosts, and any credentials configured for MDN delivery are presented to that destination.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Camel version in the project build file (for example `mvn dependency:tree | grep camel-as2`) and compare against the affected ranges from 4.0.0 to before 4.18.5 and from 4.19.0 to before 4.22.1
- Check whether the AS2 receiver accepts asynchronous MDN requests from partners and whether credentials are configured for MDN delivery

## Fix

- Upgrade Apache Camel to `4.23.0`
- Users on the 4.18.x LTS stream: upgrade to `4.18.5`
- Users on the 4.22.x LTS stream: upgrade to `4.22.1`
- Until upgraded, restrict outbound connectivity from the AS2 receiver to the partner endpoints it legitimately delivers receipts to, and do not attach MDN credentials valid for other hosts

## Timeline

- 2026-10-23T21:57:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-80344

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_