Improper Certificate Validation Affecting erlang-runtime_tools package, versions <0:23.3.4.18-2.el8ost


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.17% (7th 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-RHEL8-ERLANGRUNTIMETOOLS-18834338
  • published15 Aug 2026
  • disclosed4 Jun 2026

Introduced: 4 Jun 2026

CVE-2026-44393  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade RHEL:8 erlang-runtime_tools to version 0:23.3.4.18-2.el8ost or higher.
This issue was patched in RHSA-2026:54757.

NVD Description

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

An issue was discovered in OpenStack oslo.messaging 1.0.0 through 17.3.0. The oslo.messaging RabbitMQ driver does not perform TLS hostname verification when connecting to the message broker. When ssl_ca_file is configured, the driver enables certificate chain validation but does not pass the expected broker hostname into the underlying TLS stack. Any certificate signed by the deployment CA is accepted regardless of hostname, allowing an attacker who can intercept control-plane traffic to impersonate the RabbitMQ broker and perform a man-in-the-middle attack on RPC and notification traffic. All OpenStack services using oslo.messaging with RabbitMQ over TLS are affected.

CVSS Base Scores

version 3.1