CVE-2026-80344

waiting for further signalsZero needs more public information before it can validate it.

GHSA-wrg6-q24g-59j6 ↗EUVD-2026-104213 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+1h03mkevAttacks confirmed in the real world.
Apache Software Foundation Apache Camel >= 4.0.0, < 4.18.5; >= 4.19.0, < 4.22.1
fixed in 4.18.5, 4.22.1
CWE-918 Server-Side Request Forgery (SSRF)
ETK-2026-2051Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 07h 28msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0mpublic poc+63mwaiting for further signals+219m
0
+15min
+30min
+45min

description

Apache Camel's camel-as2 component is affected in versions before 4.18.5 on the 4.18.x line and before 4.22.1 on the 4.22.x line. A remote AS2 sender able to request asynchronous message receipts may cause the Camel host to contact an attacker-selected destination, potentially exposing network-reachable services or receipt-delivery credentials.

mitigation

Upgrade camel-as2 to Apache Camel 4.18.5, 4.22.1, or a later fixed release. Until upgraded, restrict AS2 receiver egress to approved partner receipt endpoints and avoid using broadly valid credentials for receipt delivery.

fixed in 4.18.5, 4.22.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.41%34th percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 10:28Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+1h03m
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-19 10:28Z
    cve_org: trigger signal, started the run
  2. 2026-10-19 11:32Z

this entry in the feed

GET /api/v1/feed/CVE-2026-80344

{
  "etk_id": "ETK-2026-2051",
  "cve_id": "CVE-2026-80344",
  "display_id": "CVE-2026-80344",
  "ghsa_id": "GHSA-wrg6-q24g-59j6",
  "euvd_id": "EUVD-2026-104213",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side request forgery in Apache Camel AS2",
  "summary": "Apache Camel's camel-as2 component is affected in versions before 4.18.5 on the 4.18.x line and before 4.22.1 on the 4.22.x line. A remote AS2 sender able to request asynchronous message receipts may cause the Camel host to contact an attacker-selected destination, potentially exposing network-reachable services or receipt-delivery credentials.",
  "mitigation": "Upgrade camel-as2 to Apache Camel 4.18.5, 4.22.1, or a later fixed release. Until upgraded, restrict AS2 receiver egress to approved partner receipt endpoints and avoid using broadly valid credentials for receipt delivery.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Camel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, < 4.18.5",
        ">= 4.19.0, < 4.22.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.18.5",
        "4.22.1"
      ],
      "package_name": "org.apache.camel:camel-as2",
      "purl": null
    }
  ],
  "cwes": [
    918
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
  "epss_score": 0.0041,
  "epss_percentile": 0.3407,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.557940966666667,
  "t0_at": "2026-10-19T10:28:48.809000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-19T11:32:04.362770+00:00",
      "days": 0.04393002048611111,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T10:28:48.809000+00:00",
      "url": "https://github.com/oscerd/CVE-2026-80344"
    },
    "trigger_signal": {
      "at": "2026-10-19T10:28:48.809000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T10:28:48.809000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-80344"
    }
  }
}

published 2026-10-19 11:05Z
last change 2026-10-21 20:50Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.