Skip to content

VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOM

Low severity GitHub Reviewed Published Nov 25, 2025 in VictoriaMetrics/VictoriaMetrics • Updated Nov 27, 2025

Package

gomod github.com/VictoriaMetrics/VictoriaMetrics (Go)

Affected versions

>= 1.123.0, < 1.129.1
>= 1.111.0, < 1.122.8
>= 1.0.0, < 1.110.23

Patched versions

1.129.1
1.122.8
1.110.23

Description

Impact

Affected versions are vulnerable to DoS attacks because the snappy decoder ignored VictoriaMetrics request size limits allowing malformed blocks to trigger excessive memory use. This could lead to OOM errors and service instability. The fix enforces block-size checks based on MaxRequest limits.

Patches

Versions 1.129.1, 1.122.8, 1.110.23

Resources

Note

VictoriaMetrics' security model assumes its APIs are properly secured (e.g. via access control flags or a firewall); this advisory addresses malicious input that should not be possible under a correctly secured deployment.

References

@arkid15r arkid15r published to VictoriaMetrics/VictoriaMetrics Nov 25, 2025
Published to the GitHub Advisory Database Nov 25, 2025
Reviewed Nov 25, 2025
Published by the National Vulnerability Database Nov 25, 2025
Last updated Nov 27, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(16th percentile)

Weaknesses

Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. Learn more on MITRE.

CVE ID

CVE-2025-65942

GHSA ID

GHSA-66jq-2c23-2xh5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.