OpenZipkin Zipkin resource exhaustion in HTTP collector decompression
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
Zipkin, the OpenZipkin distributed tracing server, has a flaw in its HTTP collector's handling of compressed request data. A remote attacker who can reach the server without logging in can send highly compressed data that causes it to expand excessively, which can degrade availability.
Written by a model
Original description
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.
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133608 (OpenZipkin HTTP Collector ZipkinHttpCollector.java UnzippingBytesRequestConverter.convertRequest data amplification), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133608 (entry last updated 2026-11-20):
Affected:
- OpenZipkin Zipkin: versions 3.6.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133608 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133608 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openzipkin/zipkin/pull/3838
- https://github.com/openzipkin/zipkin/issues/3834
- https://vuldb.com/vuln/441147
- https://vuldb.com/vuln/441147/cti
- https://vuldb.com/cve/CVE-2026-133608
- https://vuldb.com/submit/1050070
- https://github.com/openzipkin/zipkin/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133608
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133608"}.Affected versions
- OpenZipkin Zipkin3.6.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 9
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133608 |
| Record | NVD · CVE-2026-133608 |
| Other links 7 | |
| Advisory | VulDB · Advisory #441147 |
| Advisory | VulDB · Threat intelligence #441147 |
| Advisory | VulDB · CVE-2026-133608 record |
| Advisory | VulDB · Submission #1050070 |
| Patch | GitHub · openzipkin/zipkin · Pull request #3838 |
| Report | GitHub · openzipkin/zipkin · Issue #3834 |
| Repository | GitHub · openzipkin/zipkin · Repository |
Questions about CVE-2026-133608
Is CVE-2026-133608 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133608?
Zipkin: version 3.6.1.
Source: cve.now feed data
Related
- CVE-2026-82265Zipkin Unauthenticated Spring Boot Actuator Endpoints Exposure
- CVE-2026-103025bep/imagemeta: Unbounded memory allocation decoding PNG `zTXt` "Raw profile type iptc" chunks
- CVE-2026-132140DrayTek Vigor2960 Apmcfg Upload mainfunction.cgi null pointer dereference
- CVE-2026-128242actix-http before 3.20.1 and actix-web before 4.18.2 Decompression Bomb DoS via encoding::Decoder
- CVE-2026-122323Kyverno 1.11.0 before 1.19.2 Memory Exhaustion via Notary Signature Decompression
- CVE-2026-122322Kyverno from 1.11.0 before 1.19.2 Memory Exhaustion via Notary Attestation Decompression
No corrections so far. Something wrong on this page? Report an error.