Homepage

Improper Input 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.3% (23rd 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-18968137
  • published19 Aug 2026
  • disclosed18 Aug 2026
Report a new vulnerability Found a mistake?

Introduced: 18 Aug 2026

NewCVE-2026-61634  (opens in a new tab)
CWE-20  (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, the AMQP connection tuning path records the negotiated AMQP frame_max value, but src/main/java/com/rabbitmq/client/impl/SocketFrameHandler.java and NettyFrameHandlerFactory continue to validate broker-controlled frame payload lengths against maxInboundMessageBodySize because the negotiated limit is not applied consistently through setMaxInboundFramePayloadSize. A malicious or compromised broker can send a method frame larger than the negotiated frame_max during or after connection establishment, causing the client to allocate and decode a protocol-invalid frame instead of rejecting it with MalformedFrameException. The protocol violation can disrupt the affected connection and cause client-side denial of service. This issue is fixed in version 5.33.0.