Skip to content
WatchlistHigh

CVE-2026-80344Apache Camel SSRF

Server-Side Request Forgery (SSRF) vulnerability in Apache Camel AS2 component.

Published Oct 19, 2026 · Updated Oct 19, 2026 · Also known as EUVD-2026-104213

Key Facts

Patch in the next maintenance window
  • CVE-2026-80344 is a high-severity vulnerability (CVSS 8.2 v3.1) affecting org.apache.camel:camel-as2 (maven), Apache Camel.
  • It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
  • Fixed versions are available, including Apache Camel 4.18.5, Apache Camel 4.22.1, org.apache.camel:camel-as2 4.18.5.
  • Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Scores

CVSS v3.1

8.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS (30-day exploit likelihood)

n/a

Exploit maturity

Proof of concept

ATLAS score

35/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

1

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

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.

Affected Products

3 affected entries in total
ProductAffected versionsFixed in
org.apache.camel:camel-as2maven>= 4.0.04.18.5
Apache Camel>= 4.0.04.18.5

Patched Releases

Apache Camel

4.18.5, 4.22.1

org.apache.camel:camel-as2

4.18.5, 4.22.1

Timeline

  1. Publicly disclosed

    Oct 19, 2026

Weakness Type

  • CWE-918 Server-Side Request Forgery (SSRF)

FAQ

Common Questions.

Is CVE-2026-80344 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Oct 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.