Qpid Proton C through 0.40.0 can treat AMQP frames as SASL
Apache calls the flaw important: peers can send regular AMQP frames that Proton dispatches as SASL, with no username set.
58
Vulnerability1 · 1 read
CVE-2026-114230
SASL authentication bypass in Apache Qpid Proton C through 0.40.0
- CVSS
- —
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Apache Qpid Proton C can treat ordinary AMQP frames as SASL frames while dispatching SASL for peer authentication, so a remote peer can bypass authentication. No username is set afterward; impact depends on how the application treats incomplete authentication. It affects Proton C through 0.40.0.
What to do: Upgrade Apache Qpid Proton C to 0.41.1, which fixes the issue.
| Product | Affected | Fixed in |
|---|---|---|
| Apache Qpid Proton C | through 0.40.0 | 0.41.1 |
Estimated exposure
No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · 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.
- Weakness
- CWE-305