CVE-2025-65942 is a low-severity (CVSS 2.7) CWE-770 vulnerability in github.com/VictoriaMetrics/VictoriaMetrics. O3 Security confirms whether CVE-2025-65942 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
VictoriaMetrics Snappy Decoder DoS Vulnerability is Causing OOM
Real-World Exposure
github.com/VictoriaMetrics/VictoriaMetrics🐹github.com/VictoriaMetrics/VictoriaMetrics🐹github.com/VictoriaMetrics/VictoriaMetricsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
VictoriaMetrics is a scalable solution for monitoring and managing time series data. In versions from 1.0.0 to before 1.110.23, from 1.111.0 to before 1.122.8, and from 1.123.0 to before 1.129.1, 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. This issue has been patched in versions 1.110.23, 1.122.8, and 1.129.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | ≥ 1.123.0&&< 1.129.1 | 1.129.1 |
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | ≥ 1.111.0&&< 1.122.8 | 1.122.8 |
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | ≥ 1.0.0&&< 1.110.23 | 1.110.23 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/VictoriaMetrics/VictoriaMetrics. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/VictoriaMetrics/VictoriaMetrics to 1.129.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-65942 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-65942 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-65942. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-65942 in your dependencies?
O3 detects CVE-2025-65942 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.