dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2026-46384

HIGH · 7.5 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
iskorotkov/avro is a fast Go Avro codec. Prior to 2.33.0, several Avro decoder paths read attacker-controlled 64-bit values from the wire format and either narrowed them to platform-sized int before bounds-checking, or summed them with overflow-prone signed-int arithmetic. On 32-bit targets (GOARCH=386, arm, mips, wasm, etc.), the truncation paths can silently bypass byte-slice limits, select the wrong union branch, or hit the OCF negative-make panic via wrap. Three sub-issues are not 32-bit-specific: cumulative-size arithmetic overflow in arrayDecoder.Decode / mapDecoder.Decode / mapDecoderUnmarshaler.Decode (wraps at math.MaxInt64 on amd64 / arm64 and bypasses MaxSliceAllocSize / MaxMapAllocSize), math.MinInt negation in block-header handling, and make([]byte, size) with a negative size in OCF block reads — all three panic or bypass caps on any platform, giving an attacker a denial-of-service primitive there. This vulnerability is fixed in 2.33.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The iskorotkov/avro Go library before 2.33.0 contains multiple integer overflow and truncation vulnerabilities in its Avro decoder. Attacker-controlled 64-bit values from the wire format can trigger truncation issues on 32-bit platforms (bypassing slice limits, wrong union branch selection, OCF panics), or arithmetic overflow in array/map decoders and negative size in make() calls on any platform. These provide denial-of-service primitives.

MitigationUpgrade iskorotkov/avro to version 2.33.0 or later. Review affected code paths (Avro decoding of arrays, maps, unions, and OCF blocks) and validate that no denial-of-service conditions can occur with malicious input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify iskorotkov/avro library version
    Run 'go list -m all' or check go.mod for iskorotkov/avro version. Compare the version to 2.33.0 - versions before 2.33.0 are affected.
    Affected if Installed version is lower than 2.33.0
  2. Determine platform architecture
    Run 'go env GOARCH' or check system architecture. On 32-bit platforms (386, arm, arm64-32), 64-bit value truncation during bounds-checking is exploitable.
    Affected if Running on 32-bit architecture (386, arm, arm64-32)
  3. Identify Avro data file parsing code
    Search codebase for usage of avro.Decoder, avro.NewDecoder, or schema-specific decoder functions that process Avro binary data from external sources.
    Affected if Codebase parses Avro data from untrusted or external sources using the avro library
  4. Check for array and map decoder usage
    Search for code that decodes Avro array or map types using the avro library - look for patterns like Decoder.DecodeArray, Decoder.DecodeMap, or generic Decode calls on array/map schemas.
    Affected if Application decodes Avro array or map types from wire format
  5. Check for OCF (Object Container File) block decoder usage
    Search for avro.NewDecoderFromFile or similar functions that read Avro OCF files/blocks, or code that handles block headers in custom decoders.
    Affected if Application reads Avro OCF files or processes block headers from external Avro data

Environment is affected if iskorotkov/avro version is below 2.33.0 AND the application parses Avro data (especially arrays, maps, or OCF blocks) from external sources, with heightened risk on 32-bit platforms.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade iskorotkov/avro to version 2.33.0 or later. Review affected code paths (Avro decoding of arrays, maps, unions, and OCF blocks) and validate that no denial-of-service conditions can occur with malicious input.

Recommended fix High confidence

2.33.0

  1. Identify the project using iskorotkov/avro as a dependency (check go.mod files for 'github.com/iskorotkov/avro')
  2. Run 'go get github.com/iskorotkov/[email protected]' to upgrade to the fixed version
  3. Run 'go mod tidy' to update go.mod and go.sum
  4. Verify the upgrade by running 'go list -m all' to confirm the installed version is 2.33.0
  5. Rebuild and test the application to ensure compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46384 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data