CVE-2025-65942

CVE-2025-65942 is a low-severity allocation of resources without limits or throttling vulnerability in github.com/VictoriaMetrics/VictoriaMetrics (go), affecting versions >= 1.123.0, < 1.129.1. It is fixed in 1.129.1, 1.122.8, 1.110.23.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOM

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.

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.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2025-65942 has a CVSS score of 2.7 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.129.1, 1.122.8, 1.110.23); upgrading removes the vulnerable code path.

Affected versions

github.com/VictoriaMetrics/VictoriaMetrics (>= 1.123.0, < 1.129.1) github.com/VictoriaMetrics/VictoriaMetrics (>= 1.111.0, < 1.122.8) github.com/VictoriaMetrics/VictoriaMetrics (>= 1.0.0, < 1.110.23)

Security releases

github.com/VictoriaMetrics/VictoriaMetrics → 1.129.1 (go) github.com/VictoriaMetrics/VictoriaMetrics → 1.122.8 (go) github.com/VictoriaMetrics/VictoriaMetrics → 1.110.23 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Versions 1.129.1, 1.122.8, 1.110.23

Frequently Asked Questions

  1. What is CVE-2025-65942? CVE-2025-65942 is a low-severity allocation of resources without limits or throttling vulnerability in github.com/VictoriaMetrics/VictoriaMetrics (go), affecting versions >= 1.123.0, < 1.129.1. It is fixed in 1.129.1, 1.122.8, 1.110.23. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
  2. How severe is CVE-2025-65942? CVE-2025-65942 has a CVSS score of 2.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of github.com/VictoriaMetrics/VictoriaMetrics are affected by CVE-2025-65942? github.com/VictoriaMetrics/VictoriaMetrics (go) versions >= 1.123.0, < 1.129.1 is affected.
  4. Is there a fix for CVE-2025-65942? Yes. CVE-2025-65942 is fixed in 1.129.1, 1.122.8, 1.110.23. Upgrade to this version or later.
  5. Is CVE-2025-65942 exploitable, and should I be worried? Whether CVE-2025-65942 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2025-65942 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2025-65942?
    • Upgrade github.com/VictoriaMetrics/VictoriaMetrics to 1.129.1 or later
    • Upgrade github.com/VictoriaMetrics/VictoriaMetrics to 1.122.8 or later
    • Upgrade github.com/VictoriaMetrics/VictoriaMetrics to 1.110.23 or later

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo