Live › vulnerability › CVE-2026-80344
Go to dashboardThe 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Deployments running the Apache Camel camel-as2 component in the affected version ranges that receive AS2 messages and send asynchronous MDNs. Exposure depends on whether the AS2 receiver can reach the network and whether internal hosts or MDN credentials are reachable from it. Systems not using camel-as2 or on fixed versions can skip it.
No product ranges from the sources yet.
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.14.23.04.18.54.22.1Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-80344")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.