Skip to main content
No exploitation reported

CVE-2026-105031

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

No exploitation reported by the sources we read.

  • Published2026-10-29
  • WeaknessCWE-295

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-10-2910:16CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Qpid Proton Cother versions: not affected
    Affected
    • ≤ 0.40.0no fix statedsemver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-10-29

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • qpid-protonDebian:14all versions · no fixed version listed
  • qpid-protonDebian:13all versions · no fixed version listed
  • qpid-protonDebian:12all versions · no fixed version listed
  • qpid-protonAzure Linux:3all versions · no fixed version listed

Vendor advisories

  • CVE-2026-105031 Red Hat Product Security18 known affected

    qpid-proton: qpid-proton: improper certificate validation via retention of default system trust anchors

    qpid-proton.src as a component of Red Hat AMQ Clients · python-qpid-proton as a component of Red Hat OpenStack Platform 13 (Queens) · python-qpid-proton-docs as a component of Red Hat OpenStack Platform 13 (Queens) · +15 more

Full record on NVD

Fix

  1. Workaround from the vendor Red Hat Product Security CVE-2026-105031 · 18 productsConfigure the environment of affected processes to override the default OpenSSL certificate store path to `/dev/null`. This ensures that only explicitly configured CA certificates are trusted. For standalone or shell-executed processes: ``` export SSL_CERT_FILE=/dev/null ``` For systemd-managed s…
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-105031 · 18 productsAffected

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Published
2026-10-29
Last Modified
2026-11-05
NVD status
Deferred
GitHub Advisory
GHSA-75pq-3xrq-9pc6

Frequently asked questions

What is CVE-2026-105031?

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.

Is CVE-2026-105031 actively exploited?

Active exploitation of CVE-2026-105031 has not been confirmed. Its EPSS score was 0.1% on 2026-11-05, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-105031?

CVE-2026-105031 has a CVSS v3 base score of 9.1 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

Running qpid-proton? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record