DEBIAN-CVE-2026-114230: Debian/qpid-proton vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Qpid Proton Cto a version that resolves this vulnerability.Fixed in 0.41.1
Event History
Frequently Asked Questions
Which deployments are most exposed to this issue?
Deployments using Apache Qpid Proton C through version 0.40.0 are affected. The practical impact depends on whether the application permits or mishandles a peer connection that has no user name set, despite authentication not having completed.
What does an attacker need to do to trigger the bypass?
The attacker needs to send AMQP frames that claim to be SASL frames during SASL processing. Proton can dispatch those frames while authenticating the peer, allowing authentication to be bypassed.
What remediation is available?
Upgrade Apache Qpid Proton C to version 0.41.1, which fixes the issue.