CVE-2026-46385: CWE-400: Uncontrolled Resource Consumption in iskorotkov avro
iskorotkov/avro is a fast Go Avro codec. Prior to 2.33.0, the Avro array and map decoders looped over an attacker-controlled block-count value without checking the underlying reader's error state inside the loop body. Reader.ReadBlockHeader returns the count as a Go int, which is 64-bit on amd64 / arm64 targets — so a producer can declare a block of up to math.MaxInt64 (~9.2 × 10¹⁸) elements followed by EOF (or any truncated payload), and the decoder will attempt that many no-op iterations before propagating the error. The realistic ceiling is "indefinite until the worker is killed externally" — a single hostile payload pins a CPU core until the process is OOM-killed, deadline-cancelled, or terminated. Remote, unauthenticated denial-of-service. This vulnerability is fixed in 2.33.0.
AI Analysis
Technical Summary
iskorotkov/avro is a Go Avro codec that prior to version 2.33.0 contained a vulnerability where the array and map decoders looped over a block-count value controlled by an attacker without verifying the reader's error state during the loop. The block-count is returned as a 64-bit integer, allowing an attacker to specify a very large number of elements (up to math.MaxInt64). Because the decoder attempts to iterate this count before propagating any read error, a malicious payload can cause the decoder to consume CPU resources indefinitely, resulting in a denial-of-service condition. This vulnerability is fixed in version 2.33.0.
Potential Impact
An attacker can remotely and without authentication send a malicious payload that causes the Avro decoder to consume excessive CPU resources by looping an extremely large number of times. This leads to denial-of-service by pinning a CPU core until the process is killed or crashes due to resource exhaustion. There is no indication of data compromise or code execution, only resource exhaustion.
Mitigation Recommendations
Upgrade iskorotkov/avro to version 2.33.0 or later, where this vulnerability is fixed. Patch status is not explicitly stated in the vendor advisory, but the fix is included in version 2.33.0. Until upgraded, consider limiting exposure to untrusted Avro payloads to reduce risk.
CVE-2026-46385: CWE-400: Uncontrolled Resource Consumption in iskorotkov avro
Description
iskorotkov/avro is a fast Go Avro codec. Prior to 2.33.0, the Avro array and map decoders looped over an attacker-controlled block-count value without checking the underlying reader's error state inside the loop body. Reader.ReadBlockHeader returns the count as a Go int, which is 64-bit on amd64 / arm64 targets — so a producer can declare a block of up to math.MaxInt64 (~9.2 × 10¹⁸) elements followed by EOF (or any truncated payload), and the decoder will attempt that many no-op iterations before propagating the error. The realistic ceiling is "indefinite until the worker is killed externally" — a single hostile payload pins a CPU core until the process is OOM-killed, deadline-cancelled, or terminated. Remote, unauthenticated denial-of-service. This vulnerability is fixed in 2.33.0.
CVSS v4.0
Score 8.7high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
iskorotkov/avro is a Go Avro codec that prior to version 2.33.0 contained a vulnerability where the array and map decoders looped over a block-count value controlled by an attacker without verifying the reader's error state during the loop. The block-count is returned as a 64-bit integer, allowing an attacker to specify a very large number of elements (up to math.MaxInt64). Because the decoder attempts to iterate this count before propagating any read error, a malicious payload can cause the decoder to consume CPU resources indefinitely, resulting in a denial-of-service condition. This vulnerability is fixed in version 2.33.0.
Potential Impact
An attacker can remotely and without authentication send a malicious payload that causes the Avro decoder to consume excessive CPU resources by looping an extremely large number of times. This leads to denial-of-service by pinning a CPU core until the process is killed or crashes due to resource exhaustion. There is no indication of data compromise or code execution, only resource exhaustion.
Mitigation Recommendations
Upgrade iskorotkov/avro to version 2.33.0 or later, where this vulnerability is fixed. Patch status is not explicitly stated in the vendor advisory, but the fix is included in version 2.33.0. Until upgraded, consider limiting exposure to untrusted Avro payloads to reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-13T19:53:47.922Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
- Gcve Source
- db.gcve.eu
Threat ID: 6a19feb2e29bf47b500fc2a0
Added to database: 5/29/2026, 9:01:38 PM
Last enriched: 5/29/2026, 9:04:11 PM
Last updated: 5/31/2026, 4:53:42 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.