CVE-2026-114230

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

GHSA-v3qr-mjxm-7376 ↗EUVD-2026-112719 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Qpid Proton C <= 0.40.0
CWE-305 Authentication Bypass by Primary Weakness
ETK-2026-2959Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 05msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h04m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache Qpid Proton C through 0.40.0 can process application protocol traffic during SASL authentication when that traffic is presented as SASL. A remote peer may bypass authentication checks if the application accepts a connection whose user identity was not established.

mitigation

Upgrade Apache Qpid Proton C to version 0.41.1. Review applications using Proton C to ensure they reject connections that have not completed authentication or lack an authenticated user identity.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 10:19Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-29 10:19Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2959",
  "cve_id": "CVE-2026-114230",
  "display_id": "CVE-2026-114230",
  "ghsa_id": "GHSA-v3qr-mjxm-7376",
  "euvd_id": "EUVD-2026-112719",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Apache Qpid Proton C",
  "summary": "Apache Qpid Proton C through 0.40.0 can process application protocol traffic during SASL authentication when that traffic is presented as SASL. A remote peer may bypass authentication checks if the application accepts a connection whose user identity was not established.",
  "mitigation": "Upgrade Apache Qpid Proton C to version 0.41.1. Review applications using Proton C to ensure they reject connections that have not completed authentication or lack an authenticated user identity.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Qpid Proton C",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.40.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache Qpid Proton C",
      "purl": null
    }
  ],
  "cwes": [
    305
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 39.13717536666667,
  "t0_at": "2026-10-29T10:19:15.580000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T10:19:15.580000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T10:19:15.580000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114230"
    }
  }
}

published 2026-10-29 10:44Z
last change 2026-10-29 13:08Z

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.