Skip to main content

CVE-2026-80344: CWE-918 Server-Side Request Forgery (SSRF) in Apache Software Foundation Apache Camel

0
High
VulnerabilityCVE-2026-80344cvecve-2026-80344cwe-918
Published: 10/19/2026 (10/19/2026, 10:28:48 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache Camel

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.

CVSS v3.1

Score 8.2high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Affected software

Apache Software Foundation

Apache Camel

Affected versions
>=4.0.0 <4.18.5>=4.19.0 <4.22.1
Apache Software Foundation/org.apache.camel:camel-as2
pkg:maven/Apache Software Foundation/org.apache.camel:camel-as2
Affected versions
>=4.0.0 <4.18.5>=4.19.0 <4.22.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/19/2026, 11:03:20 UTC

Technical Analysis

The Apache Camel AS2 component suffers from an SSRF vulnerability (CWE-918) where the asynchronous MDN destination address is taken directly from the inbound message without proper constraints. This allows a remote partner to specify an arbitrary host for the Camel instance to connect to when delivering the MDN, potentially reaching internal network hosts and exposing credentials configured for MDN delivery. The vulnerability affects Apache Camel versions >=4.0.0 <4.18.5 and >=4.19.0 <4.22.1. The issue is resolved in Apache Camel 4.18.5, 4.22.1, and 4.23.0 by constraining the MDN destination address. Mitigation includes upgrading to these fixed versions or restricting outbound connectivity and credential usage for MDN delivery.

Potential Impact

An attacker can exploit this SSRF vulnerability to make the Apache Camel AS2 receiver connect to arbitrary hosts, including internal network resources not normally accessible externally. The outbound connection may carry credentials configured for MDN delivery, which could be exposed to attacker-controlled destinations. This can lead to unauthorized access or information disclosure within the internal network. The CVSS score of 8.2 reflects high impact on confidentiality with limited integrity impact and no availability impact.

Mitigation Recommendations

Upgrade Apache Camel to version 4.18.5 if using the 4.18.x LTS stream, 4.22.1 if using the 4.22.x LTS stream, or 4.23.0 for other users. These versions constrain the asynchronous MDN destination address to prevent SSRF. For deployments unable to upgrade immediately, restrict outbound network connectivity from the AS2 receiver to only legitimate partner endpoints and avoid attaching credentials to MDN delivery that are valid for any hosts other than those partners.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apache
Date Reserved
2026-08-26T09:43:30.068Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ad5f5a22cdf04f65643556b

Added to database: 10/19/2026, 10:49:06 UTC

Last enriched: 10/19/2026, 11:03:20 UTC

Last updated: 10/19/2026, 19:19:42 UTC

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses