CVE-2026-46384

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 56% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

May 18, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Jun 2, 2026
Patch available. Sources: github.
github Patch Available

Integer Overflow in Avro Decoder · Advisory · iskorotkov/avro · GitHub

https://github.com/iskorotkov/avro/security/advisories/GHSA-mc57-h6j3-3hmv

Vendor Advisories for CVE-2026-46384(13)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/acm-grafana-rhel9:17873164672026-08-26redhat
redhatrhacm2/acm-grafana-rhel9:17869089682026-08-19redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17854428722026-08-11redhat
redhatcryostat/cryostat-storage-rhel9:4.2.0-192026-07-29redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17849066282026-07-28redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845613762026-07-23redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845620602026-07-21redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17840606812026-07-16redhat
redhatrhacm2/acm-grafana-rhel9:17835788472026-07-16redhat
redhatrhacm2/acm-grafana-rhel9:17823837302026-06-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/hamba/avro/v2———
github.com/iskorotkov/avro/v2—2.33.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 222 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-09 13:41 UTCEG score recompute
  11. 2026-09-09 13:41 UTCVendor advisory
  12. 2026-09-09 12:39 UTCEG score recompute
  13. 2026-09-09 12:39 UTCVendor advisory
  14. 2026-09-08 22:00 UTCEPSS rescore
  15. 2026-09-07 16:01 UTCEPSS rescore
  16. 2026-09-07 13:53 UTCEG score recompute
  17. 2026-09-07 13:53 UTCVendor advisory
  18. 2026-09-07 12:41 UTCEG score recompute
  19. 2026-09-07 12:41 UTCVendor advisory
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-04 05:06 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-08-30 19:17 UTCEPSS rescore
  25. 2026-08-30 01:22 UTCEPSS rescore
Show 75 more
  1. 2026-08-28 21:41 UTCEPSS rescore
  2. 2026-08-27 14:25 UTCEPSS rescore
  3. 2026-08-27 13:35 UTCEG score recompute
  4. 2026-08-27 13:35 UTCVendor advisory
  5. 2026-08-27 13:02 UTCEG score recompute
  6. 2026-08-27 13:02 UTCVendor advisory
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-24 13:29 UTCEG score recompute
  10. 2026-08-24 13:29 UTCVendor advisory
  11. 2026-08-24 12:25 UTCEG score recompute
  12. 2026-08-24 12:25 UTCVendor advisory
  13. 2026-08-23 17:14 UTCEG score recompute
  14. 2026-08-23 17:14 UTCVendor advisory
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:54 UTCEG score recompute
  17. 2026-08-21 23:54 UTCVendor advisory
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 13:58 UTCEG score recompute
  21. 2026-08-20 13:58 UTCVendor advisory
  22. 2026-08-20 12:43 UTCEG score recompute
  23. 2026-08-20 12:43 UTCVendor advisory
  24. 2026-08-19 17:04 UTCEPSS rescore
  25. 2026-08-19 12:27 UTCEG score recompute
  26. 2026-08-19 12:27 UTCVendor advisory
  27. 2026-08-19 12:11 UTCEG score recompute
  28. 2026-08-19 12:11 UTCVendor advisory
  29. 2026-08-18 13:48 UTCEPSS rescore
  30. 2026-08-17 13:47 UTCEPSS rescore
  31. 2026-08-17 12:26 UTCEG score recompute
  32. 2026-08-17 12:26 UTCVendor advisory
  33. 2026-08-17 12:12 UTCEG score recompute
  34. 2026-08-17 12:12 UTCVendor advisory
  35. 2026-08-17 10:07 UTCEG score recompute
  36. 2026-08-17 10:07 UTCVendor advisory
  37. 2026-08-16 14:56 UTCEPSS rescore
  38. 2026-08-16 03:40 UTCEG score recompute
  39. 2026-08-16 03:40 UTCVendor advisory
  40. 2026-08-16 02:14 UTCEPSS rescore
  41. 2026-08-15 01:30 UTCEPSS rescore
  42. 2026-08-14 13:27 UTCEG score recompute
  43. 2026-08-14 13:27 UTCVendor advisory
  44. 2026-08-14 12:29 UTCEG score recompute
  45. 2026-08-14 12:29 UTCVendor advisory
  46. 2026-08-14 02:43 UTCEG score recompute
  47. 2026-08-14 02:43 UTCVendor advisory
  48. 2026-08-13 22:00 UTCEPSS rescore
  49. 2026-08-13 13:37 UTCEG score recompute
  50. 2026-08-13 13:37 UTCVendor advisory
  51. 2026-08-13 12:28 UTCEG score recompute
  52. 2026-08-13 12:28 UTCVendor advisory
  53. 2026-08-13 01:43 UTCEG score recompute
  54. 2026-08-13 01:43 UTCVendor advisory
  55. 2026-08-12 13:51 UTCEPSS rescore
  56. 2026-08-12 12:37 UTCEG score recompute
  57. 2026-08-12 12:37 UTCVendor advisory
  58. 2026-08-12 12:12 UTCEG score recompute
  59. 2026-08-12 12:12 UTCVendor advisory
  60. 2026-08-11 15:38 UTCEG score recompute
  61. 2026-08-11 15:38 UTCVendor advisory
  62. 2026-08-11 02:29 UTCEG score recompute
  63. 2026-08-11 02:29 UTCVendor advisory
  64. 2026-08-11 00:00 UTCEPSS rescore
  65. 2026-08-10 13:23 UTCEG score recompute
  66. 2026-08-10 13:23 UTCVendor advisory
  67. 2026-08-10 12:26 UTCEG score recompute
  68. 2026-08-10 12:26 UTCVendor advisory
  69. 2026-08-10 03:51 UTCVendor advisory
  70. 2026-08-09 14:46 UTCEG score recompute
  71. 2026-08-09 14:46 UTCVendor advisory
  72. 2026-08-09 13:46 UTCEPSS rescore
  73. 2026-08-09 01:40 UTCEG score recompute
  74. 2026-08-09 01:40 UTCVendor advisory
  75. 2026-08-08 16:37 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46384?
CVE-2026-46384 is a high vulnerability published on May 18, 2026. 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…
When was CVE-2026-46384 disclosed?
CVE-2026-46384 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46384 actively exploited?
CVE-2026-46384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.2% of all scored CVEs.
What is the CVSS score of CVE-2026-46384?
CVE-2026-46384 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46384?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46384, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46384

Explore →

Is Your Infrastructure Affected by CVE-2026-46384?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs