Improper Certificate Validation Affecting rhceph/alloy-rhel10 package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.14% (4th 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-RHEL9-RHCEPHALLOYRHEL10-22194516
  • published4 Nov 2026
  • disclosed28 Oct 2026

Introduced: 28 Oct 2026

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

How to fix?

There is no fixed version for RHEL:9 rhceph/alloy-rhel10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rhceph/alloy-rhel10 package and not the rhceph/alloy-rhel10 package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

The DB Tools rely on the TLS implementation in Golang’s standard library, which generally uses the system CA store. However, the crypto/x509 package also has its own internal denylist of known-bad CA certificates. Golang 1.27.3 adds the eMudhra certificates to this list.

DB Tools version 100.19.0 was compiled with Golang 1.26.8, which does not include this check.

The issue is resolved by updating to Golang 1.27.3 in DB Tools 100.20.0

CVSS Base Scores

version 3.1