cve.bz

CVE-2025-65942 victoriametrics victoriametrics

2.7 lowEPSS 0.4%Fix available

Low (2.7) in victoriametrics victoriametrics. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/VictoriaMetrics/VictoriaMetrics 1.110.23, 1.122.8, 1.129.1.

On this page
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.

Severity

CVSS 3.1

2.7 low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-11-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-65942 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-65942?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-65942?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-65942 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

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

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-66jq-2c23-2xh5Gogithub.com/VictoriaMetrics/VictoriaMetrics>=1.123.0 <1.129.11.129.1
GHSA-66jq-2c23-2xh5Gogithub.com/VictoriaMetrics/VictoriaMetrics>=1.111.0 <1.122.81.122.8
GHSA-66jq-2c23-2xh5Gogithub.com/VictoriaMetrics/VictoriaMetrics>=1.0.0 <1.110.231.110.23
GO-2025-4161Gogithub.com/VictoriaMetrics/VictoriaMetrics<1.110.23
>=1.111.0 <1.122.8
>=1.123.0 <1.129.1
1.110.23, 1.122.8, 1.129.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 15.6govulncheck-vulndb0.0.20251230T014957-150000.1.134.1SUSE-SU-2026:0037-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON