CVE-2025-65942 is a low-severity (CVSS 2.7) CWE-770 vulnerability in github.com/VictoriaMetrics/VictoriaMetrics. A fix is available for github.com/VictoriaMetrics/VictoriaMetrics — see the affected versions and patch details below.
VictoriaMetrics Snappy Decoder DoS Vulnerability is Causing OOM
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-65942.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-65942 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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
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
- https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.129.1
- https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.122.8
- https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.110.23
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | ≥ 1.123.0&&< 1.129.1 | 1.129.1go get github.com/VictoriaMetrics/VictoriaMetrics@v1.129.1 |
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | ≥ 1.111.0&&< 1.122.8 | 1.122.8go get github.com/VictoriaMetrics/VictoriaMetrics@v1.122.8 |
| 🐹Go | github.com/VictoriaMetrics/VictoriaMetrics | ≥ 1.0.0&&< 1.110.23 | 1.110.23go get github.com/VictoriaMetrics/VictoriaMetrics@v1.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-65942 can be triaged on real exposure rather than presence alone.
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 Security finds CVE-2025-65942 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.