HarborGuard / CVE
Back to search
HIGHCVE-2026-46385Published Modified CNA GitHub_M

CVE-2026-46385: iskorotkov/avro: CPU Exhaustion in Avro Decoder

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.

HarborGuard Analysis

HarborGuard analysis

Synopsis

This is a CPU-exhaustion denial-of-service in the iskorotkov/avro Go Avro codec. The array and map decoders trust an attacker-controlled 64-bit block count from the wire and loop on it without checking the reader's error state, so a single crafted payload declaring up to ~9.2 x 10^18 elements followed by EOF pins a worker CPU until the process is killed externally. The bug is reachable over the network without authentication and without any user interaction, and successful exploitation makes the decoding service unavailable. A patched-image rebuild at iskorotkov/avro 2.33.0 is available on HarborGuard for affected environments.

HarborGuard Coverage

Detection

Detection is available across every HarborGuard environment: the advisory is ingested from upstream feeds within minutes of publication and matched against Go module manifests in customer registries and build pipelines, including custom-built images that vendor iskorotkov/avro below 2.33.0.

Available
Triage

Triage is available with the CVSS v4 score of 8.7 (HIGH) applied as the baseline and reweighted by each customer's compliance policy, so internet-exposed services that decode untrusted Avro payloads route to the urgent inbox while internal-only consumers route to standard backlog inside the owning org.

Available
Patch

A patched-image rebuild at iskorotkov/avro 2.33.0 is available on HarborGuard for environments running an affected version. Customers who opt into auto-remediation get the rebuilt image, a regression-test run, and a PR opened against affected workloads automatically.

Pending upstream

Exploit Conditions

  • Network reachabilityRequired

    The attacker must be able to deliver an Avro payload to the decoder over the network (AV:N).

  • AuthenticationNot required

    PR:N: no credentials or account are needed to send the malicious payload.

  • Victim interactionNot required

    UI:N: the decoder processes the hostile payload on its own with no user action required.

  • Attack complexityDetail

    AC:L: the exploit is a single crafted block header and triggers reliably without timing or memory-layout conditions.

Blast Radius

  • Pins a CPU core on the decoding worker indefinitely until the process is OOM-killed, deadline-cancelled, or terminated.
  • Renders the affected service unavailable for legitimate Avro traffic for the duration of the stuck worker.
  • Amplifies trivially: a single small payload consumes a full core, so a handful of requests can exhaust a pool and take the service offline.
  • No confidentiality or integrity impact: data is not read or modified, only availability is affected.

How HarborGuard Handles This

Available on HarborGuard: a patched-image rebuild at iskorotkov/avro 2.33.0 is published the moment the fix is ingested, and for environments with auto-remediation enabled the platform rebuilds affected images, runs the regression suite, and opens a PR against the workloads that consume them. Median time from CVE publication to merged patch PR for high-severity issues is around 90 minutes in auto-remediation environments. Until the upgrade lands, compensating controls worth considering include capping request body size at the ingress, enforcing a per-request decode deadline or context timeout around Avro decoding, and isolating untrusted-payload consumers behind network policy so a stuck worker pool cannot starve unrelated services.

See how HarborGuard automates this

Metrics

CVSS v4.0
8.7
Severity
HIGH
Fixed in
Affected Products
1
Affected packages
  • iskorotkov / avro
    < 2.33.0
CVSS Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N