CVE-2026-133608 in Zipkin
Summary
by MITRE • 11/20/2026
A vulnerability was identified in OpenZipkin Zipkin 3.6.1. This affects the function UnzippingBytesRequestConverter.convertRequest of the file zipkin-server/src/main/java/zipkin2/server/internal/ZipkinHttpCollector.java of the component HTTP Collector. Such manipulation leads to highly compressed data. The attack can be executed remotely. The pull request to fix this issue awaits acceptance.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified in OpenZipkin Zipkin version 3.6.1 resides within the HTTP Collector component, specifically affecting the UnzippingBytesRequestConverter.convertRequest method located in the file zipkin-server/src/main/java/zipkin2/server/internal/ZipkinHttpCollector.java. This flaw is classified as a resource exhaustion vulnerability resulting from insufficient control over data compression ratios during request processing. The core technical issue stems from the application's handling of incoming HTTP requests that utilize gzip or similar compression algorithms without implementing adequate safeguards against decompression bombs, also known as zip bombs. When an attacker submits highly compressed payloads with extremely low entropy expansion rates, the server is forced to allocate excessive memory and CPU resources to decompress the data before it can be processed for tracing purposes. This behavior aligns with CWE-409, which describes improper handling of exceptionally large or complex input structures that lead to resource consumption issues such as denial of service conditions.
From an operational perspective, this vulnerability allows for remote exploitation by unauthenticated attackers who have network access to the Zipkin server instance. By sending specially crafted HTTP POST requests containing deeply nested compressed data, an attacker can trigger a disproportionate increase in memory usage and CPU load on the target system. The impact is primarily a denial of service against the distributed tracing infrastructure. Since Zipkin servers are often critical components in microservices architectures responsible for aggregating trace data from various services, exhausting their resources can lead to the loss of observability across the entire application ecosystem. This not only disrupts monitoring and debugging capabilities but may also cause cascading failures if dependent systems rely on timely responses from the tracing service or if resource exhaustion leads to broader system instability affecting other co-located processes.
This attack vector is consistent with techniques documented in the MITRE ATT&CK framework, particularly under T1496 Resource Hijacking where adversaries leverage compromised resources for denial of service or computational gain through inefficient processing loops and excessive data handling. The lack of input validation regarding compression ratios represents a common oversight in web application frameworks that prioritize performance over strict resource limits during decompression operations. Mitigation strategies should focus on implementing strict size limits for incoming requests both at the network level and within the application logic. Developers must configure maximum allowed uncompressed sizes for gzip streams and enforce timeouts to prevent long-running decompression tasks from consuming system resources indefinitely. Additionally, deploying Web Application Firewalls with rules capable of detecting anomalous compression ratios or unusually large compressed payloads can provide an additional layer of defense until a patched version is deployed. Organizations running Zipkin 3.6.1 should monitor for the acceptance and release of the pending pull request addressing this issue and apply updates promptly to restore secure operation of their tracing infrastructure.