CVE-2026-114230
Apache Qpid Proton C: Potential authentication bypass: regular AMQP frames can be sent as SASL frames
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
Apache Qpid Proton C: Potential authentication bypass: regular AMQP frames can be sent as SASL frames
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.
- Record
CVE-2026-114230- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-305
- Updated
- 2026-11-05
EUVDEUVD-2026-112719
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.
- Record
EUVD-2026-112719- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-05
GitHub AdvisoriesGHSA-v3qr-mjxm-7376
When dispatching SASL frames to authenticate the peer, Proton will also dispatch AMQP frames if...
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.
- Record
GHSA-v3qr-mjxm-7376- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-305
- Updated
- 2026-11-06
NVD
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.
- Record
CVE-2026-114230- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-305
- Updated
- 2026-11-05
OSVDEBIAN-CVE-2026-114230
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.
- Record
DEBIAN-CVE-2026-114230- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-06
OSVUBUNTU-CVE-2026-114230
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.
- Record
UBUNTU-CVE-2026-114230- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-07
OSVAZL-111742 No score
CVE-2026-114230 affecting package qpid-proton 0.40.0-15
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.
- Record
AZL-111742- Updated
- 2026-11-05
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
qpid-protonAzure Linux:3 |
through 0.40.0-15 | None known |
qpid-protonDebian:12 |
All versions, plus listed versions 0.37.0-100.37.0-20.37.0-30.37.0-40.37.0-5 Show 4 moreShow less0.37.0-60.37.0-70.37.0-80.37.0-9 |
None known |
qpid-protonDebian:13 |
All versions, plus listed versions 0.37.0-100.37.0-60.37.0-70.37.0-80.37.0-9 |
None known |
qpid-protonDebian:14 |
All versions, plus listed versions 0.37.0-100.37.0-60.37.0-70.37.0-80.37.0-9 |
None known |
qpid-protonUbuntu:16.04:LTS |
All versions, plus listed versions 0.7-20.10-2 |
None known |
qpid-protonUbuntu:18.04:LTS |
All versions, plus listed versions 0.14.0-5.10.14.0-5.1ubuntu1 |
None known |
qpid-protonUbuntu:20.04:LTS |
All versions, plus listed versions 0.22.0-3.20.22.0-3.2build10.22.0-3.30.22.0-3.3build1 |
None known |
qpid-protonUbuntu:22.04:LTS |
All versions, plus listed versions 0.22.0-5.10.22.0-5.1build10.22.0-5.1ubuntu10.22.0-5.1ubuntu2 |
None known |
qpid-protonUbuntu:24.04:LTS |
All versions, plus listed versions 0.37.0-2build10.37.0-2build20.37.0-2build40.37.0-2build5 |
None known |
qpid-protonUbuntu:26.10 |
All versions, plus listed versions 0.37.0-7build10.37.0-80.37.0-90.37.0-9build1 |
None known |
qpid-protonUbuntu:26.04:LTS |
All versions, plus listed versions 0.37.0-60.37.0-6build10.37.0-70.37.0-7build1 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| severity | CVE List, OSV | |
| affected, aliases, facts, references | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-114230 is a critical vulnerability (CVSS 9.8) in Apache Software Foundation Qpid Proton C, published October 29, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.50%, the 42nd percentile. No source names a fixed version.