Vulnerabilities in pkg:gem/fluent-plugin-opentelemetry

PACKAGE
Advisory Identifier: GHSA-2jc5-xhx8-qj6h
Advisory Summary

CVE-2026-44163 is a MODERATE (CVSS 5.3) denial of service vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Fluent plugin opentelemetry libraries in the RubyGems ecosystem. The issue involves fluent-plugin-opentelemetry has denial of service (dos) via large payloads and decompression bombs in `in_opentelemetry`. Remediation is available by upgrading affected packages to version 0.5.3.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:gem/fluent-plugin-opentelemetry

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:gem/fluent-plugin-opentelemetry. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-2jc5-xhx8-qj6h CVE-2026-44163 MODERATE fluent-plugin-opentelemetry Has Denial of Service (DoS) via Large Payloads and Decompression Bombs in `in_opentelemetry`

CVE-2026-44163 at a Glance

CVE Identifier CVE-2026-44163
GHSA Identifier GHSA-2jc5-xhx8-qj6h
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Fluent plugin opentelemetry
Package Ecosystem RubyGems
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-44163

To remediate this vulnerability, upgrade all affected Fluent plugin opentelemetry dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

fluent-plugin-opentelemetry fixed: 0.5.3
Upgrade fluent-plugin-opentelemetry to 0.5.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for fluent-plugin-opentelemetry

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-44163, inspect your project dependencies for Fluent plugin opentelemetry:

inspect dependencies for fluent-plugin-opentelemetry

Analyze the terminal output to locate any version of Fluent plugin opentelemetry in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.5.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Fluent plugin opentelemetry, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

The `fluent-plugin-opentelemetry` plugin (specifically the `in_opentelemetry` HTTP input) lacked strict size limits on incoming requests. It was discovered that the plugin read the entire request body and decompressed payloads into memory without enforcing maximum size thresholds. If the OpenTelemetry ingestion endpoint is exposed to untrusted networks, an attacker can send an excessively large HTTP request or a maliciously crafted, highly compressed payload. When the plugin attempts to read or decompress this payload, it will expand to an excessive size and it will consume significant system resources. ### Impact This vulnerability allows for a **Denial of Service (DoS)** attack via memory exhaustion. The rapid memory consumption during decompression can easily lead to an Out-of-Memory kill of the Fluentd process by the operating system. This results in the disruption of all log collection and forwarding capabilities on the affected node. ### Patches v0.5.3 ### Workarounds If an immediate upgrade is not possible, users are strongly advised to apply the following mitigations: 1. Restrict Network Access * Ensure that the OpenTelemetry ingestion ports (default `4318`) are deployed within a closed, trusted network. Use firewall rules (e.g., iptables, AWS Security Groups) to block access from untrusted networks or instances. 2. Use a Reverse Proxy * If you must expose HTTP ingestion to external sources, place a robust reverse proxy (such as Nginx) in front of Fluentd. Configure the proxy to handle the gzip decompression and enforce strict limits on both compressed and uncompressed body sizes before passing the traffic to Fluentd.

CVE-2026-44163 Affected Fluent plugin opentelemetry Versions

1 component(s)
Fixed Versions:
0.5.3
Product / Package Ecosystem Affected Versions Fixed Version
fluent-plugin-opentelemetry
RubyGems
< 0.5.3
0.5.3

References

Frequently Asked Questions

What is CVE-2026-44163?
CVE-2026-44163 is a security vulnerability in Fluent plugin opentelemetry involving fluent-plugin-opentelemetry Has Denial of Service (DoS) via Large Payloads and Decompression Bombs in `in_opentelemetry` under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Fluent plugin opentelemetry versions are affected?
Affected versions include releases prior to 0.5.3 across affected packages: fluent-plugin-opentelemetry.
What version fixes CVE-2026-44163?
Upgrading to 0.5.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is fluent-plugin-opentelemetry affected?
Yes, fluent-plugin-opentelemetry is affected in releases prior to 0.5.3. Upgrade your dependency to 0.5.3 or later.
What is the CVSS score of CVE-2026-44163?
CVE-2026-44163 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-44163?
CVE-2026-44163 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check RubyGems dependencies for CVE-2026-44163?
Run the dependency tree command: 'inspect dependencies for fluent-plugin-opentelemetry'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2jc5-xhx8-qj6h",
  "modified" : "2026-06-26T17:22:37Z",
  "published" : "2026-06-26T17:22:37Z",
  "aliases" : [ "CVE-2026-44163" ],
  "summary" : "fluent-plugin-opentelemetry Has Denial of Service (DoS) via Large Payloads and Decompression Bombs in `in_opentelemetry`",
  "details" : "The `fluent-plugin-opentelemetry` plugin (specifically the `in_opentelemetry` HTTP input) lacked strict size limits on incoming requests.\nIt was discovered that the plugin read the entire request body and decompressed payloads into memory without enforcing maximum size thresholds.\n\nIf the OpenTelemetry ingestion endpoint is exposed to untrusted networks, an attacker can send an excessively large HTTP request or a maliciously crafted, highly compressed payload.\nWhen the plugin attempts to read or decompress this payload, it will expand to an excessive size and it will consume significant system resources.\n\n### Impact\nThis vulnerability allows for a **Denial of Service (DoS)** attack via memory exhaustion. \nThe rapid memory consumption during decompression can easily lead to an Out-of-Memory kill of the Fluentd process by the operating system.\nThis results in the disruption of all log collection and forwarding capabilities on the affected node.\n\n### Patches\nv0.5.3\n\n### Workarounds\nIf an immediate upgrade is not possible, users are strongly advised to apply the following mitigations:\n\n1. Restrict Network Access\n   * Ensure that the OpenTelemetry ingestion ports (default `4318`) are deployed within a closed, trusted network. Use firewall rules (e.g., iptables, AWS Security Groups) to block access from untrusted networks or instances.\n2. Use a Reverse Proxy\n   * If you must expose HTTP ingestion to external sources, place a robust reverse proxy (such as Nginx) in front of Fluentd. Configure the proxy to handle the gzip decompression and enforce strict limits on both compressed and uncompressed body sizes before passing the traffic to Fluentd.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "fluent-plugin-opentelemetry"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.5.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.5.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fluent-plugins-nursery/fluent-plugin-opentelemetry/security/advisories/GHSA-2jc5-xhx8-qj6h"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fluent-plugins-nursery/fluent-plugin-opentelemetry/commit/ce6c1f2a7741592c8a79afbe75fded9e8ebfa92d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fluent-plugins-nursery/fluent-plugin-opentelemetry"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T17:22:37Z",
    "nvd_published_at" : null
  }
}