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.
Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 29 Oct 2026 13:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache qpid Proton-c |
|
| Vendors & Products |
Apache
Apache qpid Proton-c |
Thu, 29 Oct 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
Thu, 29 Oct 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Apache Qpid Proton C: Potential authentication bypass: regular AMQP frames can be sent as SASL frames | |
| Weaknesses | CWE-305 | |
| References |
|
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-10-29T11:09:06.927Z
Reserved: 2026-10-21T05:27:42.658Z
Link: CVE-2026-114230
No data.
Status : Deferred
Published: 2026-10-29T11:17:28.210
Modified: 2026-10-29T15:43:33.310
Link: CVE-2026-114230
No data.
OpenCVE Enrichment
Updated: 2026-10-29T12:29:12Z
-
CWE-305
Authentication Bypass by Primary Weakness