Skip to main content
VulnerabilityPublished

CVE-2025-65942: VictoriaMetrics · Unthrottled Resource Allocation

Affects VictoriaMetricsSource GCVE Database

0
Compare

Not known to be exploited · CVSS 2.7 Low · fixed in 1.129.1 : update VictoriaMetrics when convenient.

Data as of 19 Nov 2026, 02:30 UTC

CVSS 3.1 base score
2.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.12.7
Patch
Available – fixed in 1.129.1, 1.122.8, 1.110.23
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade VictoriaMetrics to 1.129.1, 1.122.8 or 1.110.23.

Affected software

ProductAffectedFixed in
VictoriaMetrics VictoriaMetricsAffected
  • >=1.0.0 <1.110.23
  • >=1.111.0 <1.122.8
  • >=1.123.0 <1.129.1
Fixed in
  • 1.110.23
  • 1.122.8
  • 1.129.1

AI-suggested

Upgrade VictoriaMetrics to version 1.110.23, 1.122.8, or 1.129.1 or later, where the vulnerability is patched by enforcing block-size checks based on MaxRequest limits. No other mitigation is indicated or required.

Description

VictoriaMetrics versions 1.0.0 to before 1.110.23, 1.111.0 to before 1.122.8, and 1.123.0 to before 1.129.1 contain a vulnerability where the snappy decoder ignores request size limits, allowing malformed blocks to cause excessive memory use. This can lead to out-of-memory (OOM) errors and service instability. The issue has been fixed in versions 1.110.23, 1.122.8, and 1.129.1 by enforcing block-size checks based on MaxRequest limits.

References

Community reviews

Loading reviews…