Homepage

Improper Certificate Validation Affecting conductor-fips package, versions <3.32.1-r1

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.18% (9th 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-CHAINGUARDLATEST-CONDUCTORFIPS-18968061
  • published19 Aug 2026
  • disclosed18 Aug 2026
Report a new vulnerability Found a mistake?

Introduced: 18 Aug 2026

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

How to fix?

Upgrade Chainguard conductor-fips to version 3.32.1-r1 or higher.

NVD Description

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

The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, com.rabbitmq.client.ConnectionFactory.useSslProtocol() and ConnectionFactory.useSslProtocol(String) configure com.rabbitmq.client.TrustEverythingTrustManager and leave hostname verification disabled, causing arbitrary server certificates, including self-signed certificates, to be accepted. A network attacker able to intercept a TLS connection can impersonate the RabbitMQ broker, read protected AMQP traffic, and modify traffic without certificate or hostname validation. The fix changes the production TLS helpers to use the JVM default trust store and enables hostname verification, while retaining an explicitly named development-only no-verification helper. This issue is fixed in version 5.33.0.