# CVE-2026-115942: Apache Qpid Proton C stack read overflow in TLS certificate validation

Source: https://junglewise.ai/threats/cve-2026-115942-a-misconfigured-wildcard-tls-certificate-causes-a-stack-read  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-29. Updated: 2026-10-29  
License: CC BY 4.0 with a link back

CVE-2026-115942 · Severity: info · Published 2026-10-29

Apache Qpid Proton C, a messaging library used in distributed systems, improperly validates TLS certificates with misconfigured wildcards, leading to a stack read overflow. An attacker exploiting this could read sensitive data from memory or cause application instability. The vulnerability only affects non-compliant wildcard certificates; compliant RFC 9525 certificates are unaffected.

Technologies: [Apache Qpid Proton C](https://junglewise.ai/threats/technologies/qpid-proton-c). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-115942 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-115942 being exploited in the wild.

**How severe is CVE-2026-115942?** Informational severity, published 29 October 2026.

**Which products and versions are affected?** Apache Qpid Proton C through 0.40.0.

**Is there a fix for CVE-2026-115942?** Yes: fixed in Apache Qpid Proton C 0.41.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-115942 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-115942?** Check whether you run Apache Qpid Proton C at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Apache Qpid Proton C 0.41.1

## Technical details

A stack read overflow occurs when processing misconfigured wildcard TLS certificates in Apache Qpid Proton C through version 0.40.0. The vulnerability is triggered during TLS certificate validation and can leak stack memory. The fix restricts certificate acceptance to RFC 9525-compliant certificates only, eliminating the vulnerable code path.

## Affected products

- Apache Qpid Proton C through 0.40.0

## Timeline

- 2026-10-29: disclosed

## References

- [https://lists.apache.org/thread.html/5z8x4c1939rxs5hod7q7gvgdmjd7p7pt](https://lists.apache.org/thread.html/5z8x4c1939rxs5hod7q7gvgdmjd7p7pt)

## Related threats

- [Apache Qpid Proton C SASL authentication bypass](https://junglewise.ai/threats/cve-2026-114230-when-dispatching-sasl-frames-to-authenticate-the-peer-proton)
- [Apache Qpid Proton C stack overflow in message body decoder](https://junglewise.ai/threats/cve-2026-105042-a-message-body-that-is-deeply-nested-and-decoded-by-pn-message)
- [Apache Qpid Proton C certificate validation bypass in TLS configuration](https://junglewise.ai/threats/cve-2026-105031-when-using-the-openssl-tls-implementation-both-the-pn-ssl-domain)