# CVE-2026-114230: Apache Qpid Proton C: Potential authentication bypass: regular AMQP frames can be sent as SASL frames


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114230, GHSA-v3qr-mjxm-7376

## What is CVE-2026-114230?

CVE-2026-114230 is a vulnerability in Apache Qpid Proton C, published on 29 Oct 2026. 

### Official 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.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2026-114230?


## How do I fix CVE-2026-114230?

No fix has been published for CVE-2026-114230 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114230 being exploited?

There is no known exploitation of CVE-2026-114230 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114230 and fix it if it is affected.

What it is: CVE-2026-114230 is a vulnerability in Apache Qpid Proton C, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114230 in the wild and no public exploit code.

Affected product: Apache Qpid Proton C. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114230/ (Markdown: https://insights.sbomify.com/CVE-2026-114230/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114230
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114230
- OSV: https://osv.dev/vulnerability/CVE-2026-114230

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114230/
Summaries are generated and may contain mistakes; the official description above is the record.