CVE-2026-115942 Apache Qpid Proton C: Verifying non compliant TLS wildcard cert can cause stack buffer overflow read
Not scored
Published
Updated
Check this codebase for CVE-2026-115942 and fix it if it is affected.
What it is: CVE-2026-115942 is a vulnerability in Apache Qpid Proton C, published on 29 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-115942 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-115942/ (Markdown: https://insights.sbomify.com/CVE-2026-115942/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-115942?
CVE-2026-115942 is a vulnerability in Apache Qpid Proton C, published on 29 Oct 2026.
Official description
A misconfigured wildcard TLS certificate causes a stack read overflow.
This issue does not affect any wildcard certificate issued to the RFC9525 standard - the fix only accepts certificates that comply to this standard.
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-125
Which versions are affected by CVE-2026-115942?
How do I fix CVE-2026-115942?
No fix has been published for CVE-2026-115942 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-115942 being exploited?
There is no known exploitation of CVE-2026-115942 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2026-115942, GHSA-h5r3-v75j-gx8v.