# CVE-2026-80344: Apache Camel: Camel-AS2 Server-Side Request Forgery and Credential Disclosure via Asynchronous MDN Delivery Address

> Remote attackers can force Apache Camel AS2 receivers to connect to arbitrary internal hosts and leak MDN delivery credentials.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-wrg6-q24g-59j6

## What is CVE-2026-80344?

CVE-2026-80344 is a high-severity server-side request forgery vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-80344?


## How do I fix CVE-2026-80344?

No fix has been published for CVE-2026-80344 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80344 being exploited?

There is no known exploitation of CVE-2026-80344 in the wild and no public exploit code.

Public exploit code:

- Reproducer for CVE-2026-80344 (Apache Camel camel-as2): asynchronous MDN SSRF + credential disclosure — the receiver delivers the MDN to the sender-chosen Receipt-Delivery-Option, presenting its credentials to an attacker-chosen host — Camel Spring Boot + Camel Quarkus (github_poc): https://github.com/oscerd/CVE-2026-80344

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80344 and fix it if it is affected.

What it is: CVE-2026-80344 is a high-severity server-side request forgery vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80344 in the wild and no public exploit code.

Affected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80344/ (Markdown: https://insights.sbomify.com/CVE-2026-80344/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80344
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80344
- OSV: https://osv.dev/vulnerability/CVE-2026-80344

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80344/
Summaries are generated and may contain mistakes; the official description above is the record.