Integer Overflow or Wraparound Affecting opentelemetry-collector-contrib package, versions <0:0.161.0-0.1.hum1


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.41% (33rd 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-19895166
  • published22 Sept 2026
  • disclosed16 Sept 2026

Introduced: 16 Sep 2026

CVE-2026-77406  (opens in a new tab)
CWE-190  (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, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQos is absent. Values such as -1 therefore wrap to 65535 or 4294967295 instead of being rejected. An application that permits untrusted configuration of these Qos values can unintentionally request extremely large prefetch limits, allowing a broker to deliver enough queued messages to exhaust client memory and disrupt processing. This issue is fixed in version 1.13.0.

CVSS Base Scores

version 3.1