iskorotkov/avro: CPU Exhaustion in Decoder
CVE-2026-46385GHSA-w8j3-pq8g-8m7w
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/hamba/avro/v2
- Affected
- every version
- Fixed in
- no fixed version recorded
Go github.com/iskorotkov/avro/v2
- Affected
- < 2.33.0
- Fixed in
- 2.33.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-5046 lists affected ranges: Go github.com/iskorotkov/avro/v2 >=0 =0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-w8j3-pq8g-8m7w lists affected ranges: Go github.com/iskorotkov/avro/v2 >=0 <2.33.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.7 · 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 · score source
- EPSS
- CVE-2026-46385: 0.61% estimated exploitation activity in the next 30 days; percentile 49.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
CPU Exhaustion in Avro Decoder via Unbounded Block-Count Iteration Summary 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. The fix exits the loop on the first inner-decode error. It does not bound the loop length itself; for full coverage on untrusted inputs, also configure Config.MaxSliceAllocSize and Config.MaxMapAllocSize (the latter introduced…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-w8j3-pq8g-8m7w
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GO-2026-5046
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-46385 Advisory: iskorotkov/avro: CPU Exhaustion in Decoder IDs: CVE-2026-46385, GHSA-w8j3-pq8g-8m7w Record: https://patchnext.com/advisories/cve-2026-46385 (revision 3, source checked 26 Oct 2026, 15:23 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/iskorotkov/avro/v2 2.33.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/hamba/avro/v2: affected every version - Go github.com/iskorotkov/avro/v2: affected < 2.33.0; fixed in 2.33.0 ## Suggested inspection (read-only) - Go github.com/hamba/avro/v2: check the installed version with your package manager. - Go github.com/iskorotkov/avro/v2: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/hamba/avro/v2, github.com/iskorotkov/avro/v2. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GO-2026-5046 (OSV record GO-2026-5046 lists affected ranges: Go github.com/iskorotkov/avro/v2 >=0 =0) - Verified: https://github.com/advisories/GHSA-w8j3-pq8g-8m7w (GitHub-reviewed advisory GHSA-w8j3-pq8g-8m7w lists affected ranges: Go github.com/iskorotkov/avro/v2 >=0 <2.33.0) Commands are suggestions: review each one before running it.
Loading voting…