Skip to main content
VulnerabilityPublished

CVE-2026-114230: Apache Qpid Proton C · Authentication Bypass by Primary Weakness

Affects Apache Qpid Proton CSource CVE Database V5

0
Compare

Not known to be exploited · fixed in 0.41.1 : patch Apache Qpid Proton C soon.

Data as of 29 Oct 2026, 11:32 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 0.41.1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Qpid Proton CAffected
  • <=0.40.0
Fixed in–

AI-suggested

Users should upgrade Apache Qpid Proton C to version 0.41.1 or later, where this authentication bypass vulnerability is fixed. No other mitigation is specified by the vendor advisory.

Description

When dispatching SASL frames to authenticate the peer, Proton will also dispatch AMQP frames if they claim to be SASL frames. This allows authentication bypass. However there will be no user name set so the effects depend on how the application deals with this condition - which otherwise means that authentication has not completed yet. This issue affects Apache Qpid Proton C: through 0.40.0. Users are recommended to upgrade to version 0.41.1, which fixes the issue.

References

Community reviews

Loading reviews…