HighPublic exploitVulnerability

CVE-2026-80344

SSRF in Apache Camel AS2 Asynchronous MDN Delivery

Published Oct 19, 2026 · Updated 3 days ago

Trending this weekNot trendingOutside this week’s top 100

Mention activity · 30 days

7 mentions · peak 4 in a dayToday

CVSS8.2High · v3.1

EPSS0.49%42nd percentile

CISA KEVNoNot listed

In the wildNonePublic exploit, no exploitation reported

Vendor: Apache Software Foundation

IdentifiersCVE-2026-80344CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2026-80344 is a server-side request forgery vulnerability in Apache Camel's AS2 component (camel-as2), affecting versions 4.0.0 through versions before 4.18.5 and 4.19.0 through versions before 4.22.1. The component uses the asynchronous Message Disposition Notification (MDN) destination supplied in an inbound AS2 message without constraining it to deployment-configured destinations. A remote sender can therefore cause the AS2 receiver to deliver a receipt to an attacker-selected host, including internal network hosts. Credentials configured for outbound MDN delivery may also be disclosed if they accompany the connection.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.

Check your exposure

Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can induce outbound connections from the AS2 receiver to attacker-selected destinations, including resources reachable only from the deployment's internal network. This bypasses the network reachability restrictions normally imposed on the attacker. When MDN delivery includes configured credentials, those credentials can be presented to an attacker-controlled destination, resulting in credential disclosure.

Mitigation

If you can’t patch tonight, do this now.

Until an upgrade is possible, restrict outbound connectivity from the AS2 receiver to legitimate partner endpoints required for receipt delivery. Do not attach MDN-delivery credentials that are valid for hosts other than those legitimate partners.

Remediation

Patch, then assume compromise.

Upgrade to Apache Camel 4.23.0, or to 4.18.5 for the 4.18.x LTS stream or 4.22.1 for the 4.22.x LTS stream. These releases constrain asynchronous MDN destinations instead of accepting sender-supplied addresses verbatim. The end-of-life 4.14.x release stream does not receive the fix; migrate to a supported, patched release.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →

CVE-2026-80344The repository contains two self-contained Java reproducers of a claimed Apache Camel AS2 asynchronous MDN SSRF and credential-disclosure vulnerability. Its 19 files comprise seven Java source files, three READMEs, two Maven POMs, two Dockerfiles, two Compose definitions, two application-property files, and a .gitignore. Spring Boot uses version 3.5.13 with Camel 4.22.0; Quarkus uses version 3.29.0 with Camel Quarkus AS2 3.29.0, documented as bundling Camel 4.15.0. These are application runtimes, not exploit frameworks. Each module defines an AS2 receiver and sender in As2Routes.java, a loopback HTTP recorder in InternalSink.java, and an HTTP attack/report handler in ExploitController.java or ExploitResource.java. Spring Boot additionally has an explicit Application.main entry point. The attack handler clears recorded hits, sends a fixed unsigned EDIFACT message requesting an asynchronous MDN, and polls for approximately ten seconds after the send returns. The sink records the request method, URI, and Authorization header and responds with HTTP 200. Although the configured destination path is /internal-mdn-sink, the sink registers the root context and accepts other paths as well. The exploit mechanism is sender control of Receipt-Delivery-Option: the receiver delivers an MDN to an internal destination and may attach configured delivery credentials. This demonstrates constrained HTTP SSRF through MDN delivery, not arbitrary HTTP-method control or code execution. All traffic destinations and credentials are local fixtures; no external collection infrastructure or destructive behavior is present. The README claims affected Camel ranges of 4.0.0 through versions before 4.18.5 and 4.19.0 through versions before 4.22.1, with fixes in 4.18.5, 4.22.1, and 4.23.0. It describes asyncMdnAllowedHosts as the destination restriction and states patched builds withhold credentials from non-allow-listed hosts. Neither module actually configures that option. CVE attribution, version claims, dependency availability, and runtime success have not been independently verified. A missing sink hit is not conclusive evidence of patching: startup, routing, delivery, or timeout failures can produce the same result despite the handler labeling it patched. Repository URL, Git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.oscerd · Disclosed Oct 19, 2026 · java · networkOperational

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

Apache Software FoundationCamelapplication

External references

References

MITRE CVEcve.org · CVE-2026-80344 NVDnvd.nist.gov/vuln/detail/CVE-2026-80344 MITRE CWE · CWE-918Server-Side Request Forgery (SSRF)camel.apache.orgcamel.apache.org/security/CVE-2026-80344.html github.comgithub.com/apache/camel/pull/25637 github.comgithub.com/apache/camel/pull/25763 github.comgithub.com/apache/camel/pull/25764 issues.apache.orgissues.apache.org/jira/browse/CAMEL-24417

Activity feed

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →

ghsa syntheticNews · Oct 19, 2026GHSA-wrg6-q24g-59j6Apache Camel's AS2 component uses a sender-supplied asynchronous Message Disposition Notification (MDN) destination without restricting it to configured partner endpoints. A remote partner can cause the AS2 receiver to connect to attacker-selected destinations, including internal-only hosts, and potentially expose credentials configured for MDN delivery. Fixed releases are 4.18.5, 4.22.1, and 4.23.0. Interim mitigations are to restrict receiver outbound connectivity to legitimate partner endpoints and ensure MDN credentials are not valid for other hosts.Read more ↗cvefeed high severityNews · Oct 19, 2026CVE-2026-80344 - Apache Camel: Camel-AS2 Server-Side Request Forgery and Credential Disclosure via Asynchronous MDN Delivery AddressA high-severity vulnerability in Apache Camel's AS2 component allows a remote sender to control the destination for asynchronous Message Disposition Notifications (MDNs), enabling server-side requests to internal hosts and disclosure of credentials attached to MDN delivery. The reported CVSS 3.1 score is 8.2, with no privileges or user interaction required. Affected versions are 4.0.0 through versions before 4.18.5, and 4.19.0 through versions before 4.22.1. Fixes are available in 4.18.5, 4.22.1, and 4.23.0. Interim mitigations include restricting outbound AS2 receipt traffic to legitimate partner endpoints and limiting MDN credentials to those partners.Read more ↗camel apacheNews · Oct 15, 2026Apache Camel Security Advisory - CVE-2026-80344 - Apache CamelApache Camel's camel-as2 component accepts a remote sender-supplied asynchronous Message Disposition Notification (MDN) destination without restricting it to configured partner endpoints. This allows server-side request forgery to attacker-selected destinations, including internal hosts, and disclosure of credentials configured for outgoing MDN delivery. Fixed releases are 4.23.0, 4.22.1, and 4.18.5. The end-of-life 4.14.x branch does not receive the fix. Interim mitigations are to restrict AS2 receiver outbound connectivity to legitimate partner endpoints and ensure MDN credentials are valid only for those partners.Read more ↗

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.

Check your exposure

Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.

Start Free Trial Open in App ↗

Exposure mappingQuery your assets running an affected version, and investigate the blast radius.

Threat actor evidenceEvery report linking this CVE to a named adversary.

Associated malwareMalware families linked to this CVE, with evidence and IOCs.

Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.

Social activity3Community discussion across Reddit, Mastodon, and other social sources.