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
The iskorotkov avro Go library versions before 2.33.0 contain a vulnerability where the Avro array and map decoders iterate over a block-count value provided by an attacker without verifying the reader's error state inside the loop. The reader returns the count as a 64-bit integer, allowing an attacker to specify an extremely large block count (up to math.MaxInt64) followed by truncated or invalid data. The decoder attempts to perform a very large number of no-op iterations before propagating the error, causing indefinite CPU consumption and effectively a remote denial-of-service condition. This issue is tracked as CWE-400 (Uncontrolled Resource Consumption) and CWE-835 (Loop with Unreachable Exit Condition). The vulnerability is fixed in version 2.33.0.
Potential Impact
A remote, unauthenticated attacker can exploit this vulnerability by sending specially crafted Avro payloads with excessively large block-count values followed by truncated or invalid data. This causes the decoder to consume CPU resources indefinitely until the process is terminated or killed, resulting in denial of service. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
A fix for this vulnerability is available in iskorotkov avro version 2.33.0. Users are strongly advised to upgrade to version 2.33.0 or later to remediate this issue. Red Hat advises applying the relevant security updates when available. There are no known practical temporary workarounds that fully mitigate this issue.
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
Affected software
pkg:golang/github.com/iskorotkov/avroRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The iskorotkov avro Go library versions before 2.33.0 contain a vulnerability where the Avro array and map decoders iterate over a block-count value provided by an attacker without verifying the reader's error state inside the loop. The reader returns the count as a 64-bit integer, allowing an attacker to specify an extremely large block count (up to math.MaxInt64) followed by truncated or invalid data. The decoder attempts to perform a very large number of no-op iterations before propagating the error, causing indefinite CPU consumption and effectively a remote denial-of-service condition. This issue is tracked as CWE-400 (Uncontrolled Resource Consumption) and CWE-835 (Loop with Unreachable Exit Condition). The vulnerability is fixed in version 2.33.0.
Potential Impact
A remote, unauthenticated attacker can exploit this vulnerability by sending specially crafted Avro payloads with excessively large block-count values followed by truncated or invalid data. This causes the decoder to consume CPU resources indefinitely until the process is terminated or killed, resulting in denial of service. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
A fix for this vulnerability is available in iskorotkov avro version 2.33.0. Users are strongly advised to upgrade to version 2.33.0 or later to remediate this issue. Red Hat advises applying the relevant security updates when available. There are no known practical temporary workarounds that fully mitigate this issue.
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
- Gcve Source
- db.gcve.eu
Threat ID: 6a19feb2e29bf47b500fc2a0
Added to database: 05/29/2026, 21:01:38 UTC
Last enriched: 08/13/2026, 19:58:06 UTC
Last updated: 09/14/2026, 22:12:16 UTC
Views: 145
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.
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.