Numeric Range Comparison Without Minimum Check Affecting opentelemetry-collector-contrib package, versions <0:0.161.0-0.1.hum1


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.52% (42nd 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-RHEL10-OPENTELEMETRYCOLLECTORCONTRIB-19894107
  • published18 Sept 2026
  • disclosed16 Sept 2026

Introduced: 16 Sep 2026

CVE-2026-77403  (opens in a new tab)
CWE-839  (opens in a new tab)

How to fix?

Upgrade RHEL:10 opentelemetry-collector-contrib to version 0:0.161.0-0.1.hum1 or higher.
This issue was patched in RHSA-2026:68290.

NVD Description

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

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Connection.openTune in connection.go accepts a server-advertised FrameMax below the AMQP frameMinSize value of 4096 bytes because the connection negotiation loop does not enforce the protocol minimum. A malicious or compromised AMQP broker can therefore advertise an extremely small FrameMax, causing later client publications to be fragmented into excessive numbers of frames and write operations. This can consume CPU and stall the client or its host. This issue is fixed in version 1.13.0.

CVSS Base Scores

version 3.1