Is CVE-2025-61726 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-61726 being exploited in the wild.

How severe is CVE-2025-61726?

High severity, with a CVSS score of 7.5, published 28 January 2026.

Which products and versions are affected?

stdlib (Go) SEMVER:introduced=0,fixed=1.24.12,introduced=1.25.0,fixed=1.25.6.

Is there a fix for CVE-2025-61726?

Yes. stdlib (Go): upgrade to 1.25.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-61726 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-61726?

Check whether you run stdlib (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-61726: Go net/url memory exhaustion in query parameter parsing

CVE-2025-61726 · Severity: high · CVSS 7.5 · Published 2026-01-28

A vulnerability in the Go programming language's standard library could allow an attacker to crash a web server or application. By sending a specially crafted web request with an extremely large number of unique parameters, an attacker can force the application to consume all available system memory. This results in a denial-of-service (DoS) condition, making the service unavailable to legitimate users.

Technologies: stdlib (Go). Vendors: Go.

Quick answers

Is CVE-2025-61726 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-61726 being exploited in the wild.
How severe is CVE-2025-61726?: High severity, with a CVSS score of 7.5, published 28 January 2026.
Which products and versions are affected?: stdlib (Go) SEMVER:introduced=0,fixed=1.24.12,introduced=1.25.0,fixed=1.25.6.
Is there a fix for CVE-2025-61726?: Yes. stdlib (Go): upgrade to 1.25.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-61726 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-61726?: Check whether you run stdlib (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

stdlib (Go): upgrade to 1.25.6 or later
```
go get stdlib@v1.25.6
```

Technical details

A memory exhaustion vulnerability exists in the Go 'net/url' package and 'net/http.Request.ParseForm' method. While URL query parameters are typically constrained by request header size limits, 'ParseForm' can process large URL-encoded bodies containing a vast number of unique keys. Because the package does not enforce a maximum limit on the number of parameters, an attacker can send a crafted request that forces the application to allocate excessive memory during parsing. This can lead to a process crash or system-wide denial of service. The issue is fixed in Go versions 1.24.12 and 1.25.6.

Affected products

Google Go before 1.24.12, 1.25.0 before 1.25.6

Identifiers

CVE-2025-61726
GO-2026-4341

Timeline

2026-01-07: disclosed: Issue opened in Go repository
2026-01-28: advisory: CVE published and Go vulnerability report released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.