How severe is GHSA-66jq-2c23-2xh5?

GHSA-66jq-2c23-2xh5 has a CVSS score of 2.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-66jq-2c23-2xh5?

GHSA-66jq-2c23-2xh5 affects the following packages: github.com/VictoriaMetrics/VictoriaMetrics (Go), github.com/VictoriaMetrics/VictoriaMetrics (Go), github.com/VictoriaMetrics/VictoriaMetrics (Go). Ecosystems affected: Go.

How do I fix GHSA-66jq-2c23-2xh5?

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 GHSA-66jq-2c23-2xh5 is resolved across your whole dependency graph.

How do I detect GHSA-66jq-2c23-2xh5 in my Go dependencies?

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.

How do I mitigate GHSA-66jq-2c23-2xh5 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-66jq-2c23-2xh5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-66jq-2c23-2xh5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-66jq-2c23-2xh5?

GHSA-66jq-2c23-2xh5 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-66jq-2c23-2xh5?

GHSA-66jq-2c23-2xh5 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-66jq-2c23-2xh5 published, and has it been updated?

GHSA-66jq-2c23-2xh5 was published on November 25, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

LOW severity

VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOMGHSA-66jq-2c23-2xh5

LOWFix: VictoriaMetrics/VictoriaMetrics@51b44af

GHSA-66jq-2c23-2xh5 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.

Also known asCVE-2025-65942GO-2025-4161

Published

Nov 25, 2025

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-66jq-2c23-2xh5.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

🐹github.com/VictoriaMetrics/VictoriaMetrics🐹github.com/VictoriaMetrics/VictoriaMetrics🐹github.com/VictoriaMetrics/VictoriaMetrics

Real-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

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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/VictoriaMetrics/VictoriaMetrics`	≥ 1.123.0&&< 1.129.1	1.129.1`go get github.com/VictoriaMetrics/VictoriaMetrics@v1.129.1`
🐹Go	`github.com/VictoriaMetrics/VictoriaMetrics`	≥ 1.111.0&&< 1.122.8	1.122.8`go get github.com/VictoriaMetrics/VictoriaMetrics@v1.122.8`
🐹Go	`github.com/VictoriaMetrics/VictoriaMetrics`	≥ 1.0.0&&< 1.110.23	1.110.23`go get github.com/VictoriaMetrics/VictoriaMetrics@v1.110.23`

Detection & mitigation playbook

Open-source dependency

Detect
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 GHSA-66jq-2c23-2xh5 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-66jq-2c23-2xh5 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

2.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

CWE Classification

CWE-770CWE-770

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

VictoriaMetrics

5.4/10

Code-Review4/10

Maintained10/10

Branch-ProtectionN/A

Assessed Nov 9, 2026

Timeline

Disclosed

Nov 25, 2025

Last updated

Sep 10, 2026

Identifiers

GHSA-66jq-2c23-2xh5

GO-2025-4161

References

Advisorynvd.nist.gov · CVE 2025 65942 Webgithub.com · GHSA 66jq 2c23 2xh5 Webgithub.com · 51b44afd34d2c9a392d4ebedeeb5b4a7f5beca24 Webgithub.com · v1.110.23 Webgithub.com · v1.122.8 Webgithub.com · v1.129.1 Packagegithub.com · VictoriaMetrics

Related vulnerabilities

Also affects VictoriaMetrics

This CVE is low severity; 2 of 2 other CVEs affecting VictoriaMetrics are rated as high or higher (top: moderate).

CVE-2026-61625CVE-2025-65942

Same weakness: CWE-770

This CVE is low severity; 6 of 6 other CVEs with CWE-770 are rated as high or higher (top: high).

CVE-2026-118748CVE-2026-118750CVE-2026-114149CVE-2026-102650CVE-2026-63501CVE-2026-59171Browse all CWE-770

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

VictoriaMetrics' Snappy Decoder DoS Vulnerability is Causing OOMGHSA-66jq-2c23-2xh5

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Resources

Note

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-66jq-2c23-2xh5 in your dependencies?