Improper Certificate Validation Affecting qpid-proton-c package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.27% (20th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-QPIDPROTONC-22344830
  • published8 Nov 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

NewCVE-2026-105031  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 qpid-proton-c.

NVD Description

Note: Versions mentioned in the description apply only to the upstream qpid-proton-c package and not the qpid-proton-c package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1