Uncontrolled Memory Allocation Affecting logstash-9.2-with-output-opensearch package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.42% (35th 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-MINIMOSLATEST-LOGSTASH92WITHOUTPUTOPENSEARCH-18970094
  • published20 Aug 2026
  • disclosed18 Aug 2026

Introduced: 18 Aug 2026

CVE-2026-69219  (opens in a new tab)
CWE-789  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest logstash-9.2-with-output-opensearch.

NVD Description

Note: Versions mentioned in the description apply only to the upstream logstash-9.2-with-output-opensearch package and not the logstash-9.2-with-output-opensearch package as distributed by Minimos. See How to fix? for Minimos:latest 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.1, src/main/java/com/rabbitmq/client/impl/ValueReader.java uses ValueReader.readBytes to accept a wire-declared contentLength below Integer.MAX_VALUE and allocate a byte array before checking the bytes available in the frame. A malicious AMQP peer can send a LongString or byte-array field with type tag S and a declared length such as 0x7FFFFFFE during the pre-authentication connection.start server-properties table, causing an approximately 2 GB allocation and OutOfMemoryError before readFully consumes data. The resulting memory exhaustion can terminate the JVM and cause denial of service. This issue is fixed in version 5.33.1.