Advisory record · GHSA-66jq-2c23-2xh5

VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOM

CVSS 2.7 LowEPSS 0.0037 · 30th percentile

Published by the GitHub Advisory Database at 25 Nov 2025, 20:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/VictoriaMetrics/VictoriaMetricsGo>=1.123.0, <1.129.1 || >=1.111.0, <1.122.8 || >=1.0.0, <1.110.231.129.1, 1.122.8, 1.110.23
Identifiers
GHSA-66jq-2c23-2xh5 · CVE-2025-65942 · GO-2025-4161
Weakness (CWE)
CWE-770
Published
25 Nov 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

VictoriaMetrics versions from 1.0.0 up to (but not including) 1.110.23, from 1.111.0 up to 1.122.8, and from 1.123.0 up to 1.129.1 are affected. Snappy decoding ignored request size limits, so malformed compressed blocks could trigger excessive memory use and out-of-memory errors, a denial of service. The source does not describe a specific attacker position beyond sending malicious input to the API. Upgrade to 1.110.23, 1.122.8, or 1.129.1 depending on your release line.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.7 Low 3.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0037, the 30th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.