CVE-2026-80343

validatedZero produced an exploit or a check.

GHSA-pvjg-pwh7-34pj ↗EUVD-2026-104214 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−23h46mkevAttacks 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-178 Improper Handling of Case Sensitivity
ETK-2026-2049Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1h04mTTV
30mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
public poc−23h46mtrigger signal (cve.org) +0hcheck available+1h04magent stopped
−18h
−12h
−6h

description

Apache Camel's camel-netty-http component is affected when deployments use path-based security constraints. A remote caller can vary request-path letter case to bypass a constraint and reach a protected route; the caller only needs to be able to send requests to the consumer.

mitigation

Upgrade affected 4.18.x deployments to 4.18.5 and affected 4.19.x through 4.22.x deployments to 4.22.1. Until upgrading, enforce authorization before the Camel consumer and normalize request paths at that boundary.

fixed in 4.18.5, 4.22.1

check
available
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.45%38th percentile
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 10:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−23h46m
Δ to kevAttacks confirmed in the real world.
–

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2049",
  "cve_id": "CVE-2026-80343",
  "display_id": "CVE-2026-80343",
  "ghsa_id": "GHSA-pvjg-pwh7-34pj",
  "euvd_id": "EUVD-2026-104214",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Case-sensitive path authorization bypass in camel-netty-http",
  "summary": "Apache Camel's camel-netty-http component is affected when deployments use path-based security constraints. A remote caller can vary request-path letter case to bypass a constraint and reach a protected route; the caller only needs to be able to send requests to the consumer.",
  "mitigation": "Upgrade affected 4.18.x deployments to 4.18.5 and affected 4.19.x through 4.22.x deployments to 4.22.1. Until upgrading, enforce authorization before the Camel consumer and normalize request paths at that boundary.",
  "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-netty-http",
      "purl": null
    }
  ],
  "cwes": [
    178
  ],
  "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.0045,
  "epss_percentile": 0.382,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 29.540086,
  "t0_at": "2026-10-19T10:27:58.845000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-19T11:31:29.510988+00:00",
      "days": 0.04410493041666667,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T10:27:58.845000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-18T10:41:55+00:00",
      "days": -0.9903222800925926,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T10:27:58.845000+00:00",
      "url": "https://github.com/oscerd/CVE-2026-80343"
    },
    "trigger_signal": {
      "at": "2026-10-19T10:27:58.845000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T10:27:58.845000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-80343"
    }
  }
}

published 2026-10-19 11:01Z
last change 2026-10-21 21:30Z

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.