CVSS 3.1
8.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NHigh (8.2) in apache camel. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExplain CVE-2026-80344 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80344?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80344?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80344 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.0.0 before 4.18.5 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.22.1 |
Red Hat rates this Important.
This vulnerability is rated as Important because unauthenticated remote actors can trigger arbitrary outbound network requests directly from the application server without prior privileges. In deployments utilizing the Apache Camel AS2 component, receipt destination parameters received within incoming messages are processed without verification against a predefined allowlist. This behavior enables attackers to probe internal network services and potentially capture sensitive transmission credentials configured for asynchronous delivery confirmations.
--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to constrain asynchronous MDN receipt destinations in the AS2 receiver to an approved host allowlist before establishing outbound socket connections: upgrade to Apache Camel 4.18.5, 4.22.1, 4.23.0 (or the fixed Camel As builds), which validates target hosts against an asyncMdnAllowedHosts allowlist, strips outbound authentication credentials if unconfigured, and enforces HTTP scheme restrictions, closing all 2 injection vectors (inbound AS2 message with crafted Receipt-Delivery-Option header, unvalidated asynchronous MDN delivery address). Until patched, this is a concern on deployments exposing Camel AS2 receiver endpoints accessible to inbound network traffic, so restrict outbound network connectivity from the AS2 receiver to authorized partner endpoints and avoid attaching credentials to MDN delivery that are valid outside trusted destinations. As a compensating measure, enforce allowlist-based validation on the Receipt-Delivery-Option header value to reject arbitrary receipt destination addresses and restrict outbound network egress to only approved partner endpoints to contain connections to internal networks and metadata services. These controls limit blast radius and contain exploitation, but they do not fix the underlying unvalidated receipt destination SSRF defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1304 SSRF Prevention (Outbound Request Allowlist) (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Fuse 7 | camel-as2 | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80344.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.