CVE-2026-114230

Apache Qpid Proton C: Potential authentication bypass: regular AMQP frames can be sent as SASL frames

Published Oct 29, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

When an AMQP client dispatches a frame labeled as a SASL frame, Proton will treat it as a valid authentication attempt. The frame can carry normal AMQP payloads, causing the server to skip proper SASL authentication. Because no username is set in this scenario, the application may allow access before authentication is complete or could reject the session. This vulnerability thus creates a potential authentication bypass that could permit unauthorized actions or cause a denial of service, depending on how the application handles partially authenticated sessions.

Affected Systems

Apache Qpid Proton C provided by the Apache Software Foundation. Versions up to and including 0.40.0 are affected. Users are advised to upgrade to 0.41.1 or newer.

Risk and Exploitability

The CVSS score is 9.8 and the EPSS score is < 1%, indicating a high severity vulnerability that is unlikely to be exploited now but could be targeted in future. The vulnerability is not listed in CISA KEV. The likely attack requires network access to an AMQP endpoint so an external actor can send crafted frames that masquerade as SASL frames. Because this flaw can bypass the standard authentication workflow, the risk is high in environments that accept unauthenticated frames before completing authentication. Administrators should treat this as significant and prioritize remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Qpid Proton C to version 0.41.1 or later, which implements proper frame type checking.
  • Configure applications to reject any authentication attempts that do not include a valid username before granting access.
  • Implement network monitoring and rate limiting for AMQP authentication traffic to detect and block suspicious frame patterns.

Generated by OpenCVE AI on November 5, 2026 at 23:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
First Time appeared Apache
Apache qpid Proton-c
Vendors & Products Apache
Apache qpid Proton-c
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
Weaknesses
  • CWE-305

    Authentication Bypass by Primary Weakness

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 5, 2026, 9:29 PM
Reserved
Oct 21, 2026, 5:27 AM
Status
Deferred
Published
Oct 29, 2026, 11:17 AM
Modified
Nov 5, 2026, 10:17 PM
Severity
Important
Public date
Oct 29, 2026, 10:19 AM