CVE-2026-114230: When dispatching SASL frames to authenticate the peer, Proton will also dispatch AMQP frames if they
Source GCVE Database
Not known to be exploited · fixed in 0.41.1 : patch Apache Qpid Proton C soon.
Data as of 29 Oct 2026, 13:47 UTC
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
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software FoundationApache Qpid Proton C | Affected
| Fixed in– |
AI-suggested
Users should upgrade Apache Qpid Proton C to version 0.41.1, which contains the fix for this authentication bypass vulnerability. No other mitigation is indicated by the vendor advisory.
Description
Apache Qpid Proton C versions through 0.40.0 have a vulnerability in the SASL authentication frame dispatching process. The software incorrectly dispatches AMQP frames that claim to be SASL frames, allowing an authentication bypass. However, no user name is set during this bypass, so the impact depends on how the application handles an unauthenticated state. The issue is fixed in version 0.41.1.