LiveActive security incident?Get immediate response
CVE Record

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

The net/url package does not set a limit on the number of query parameters in a query. While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-61726 is an availability issue in Go’s URL/form parsing. A service that parses very large URL-encoded forms with many unique parameters may consume excessive memory and become slow or unavailable. The supplied sources rate it high severity, but do not show confirmed active exploitation.

Executive priority

Treat as high priority for public Go services because it can affect availability without authentication. Focus first on customer-facing APIs and forms, then internal services. There is no supplied evidence of active exploitation, so urgency is driven by exposure and downtime tolerance.

Technical view

The Go standard library net/url package lacks a limit on query parameter count. net/http.Request.ParseForm can parse large URL-encoded forms, and many unique parameters can drive excessive memory consumption. The CVSS 3.1 score is 7.5 with network, low-complexity, unauthenticated availability impact.

Likely exposure

Most relevant exposure is internet-facing Go services that call ParseForm or otherwise parse large URL-encoded request bodies. Products embedding affected Go runtime or standard library builds may also be exposed; the supplied bundle does not provide a complete product list.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. Abuse would be denial-of-service oriented: sending oversized form data with many unique parameters to memory-stress parsers. No exploit details are needed to assess operational risk.

Researcher notes

The supplied data identifies CWE-400 and CWE-770 resource-consumption weaknesses. Fixed-version details are not present in the structured affected field, so remediation should be tied to the Go advisory, Go announce post, and vendor errata rather than inferred boundaries.

Mitigation direction

  • Check the Go advisory GO-2026-4341 and Go announce post for fixed versions.
  • Apply relevant Go, platform, or Red Hat security updates when available.
  • Limit request body size and form parsing exposure at application or proxy layers.
  • Monitor public endpoints that parse URL-encoded forms for memory spikes.
  • Prioritize services where unauthenticated users can submit large forms.

Validation and detection

  • Inventory Go services using net/http Request.ParseForm or URL-encoded form parsing.
  • Confirm the Go toolchain and runtime versions used to build deployed binaries.
  • Review reverse proxy and application request size limits for form endpoints.
  • Test memory behavior with benign oversized-form regression cases in staging.
  • Check vendor advisories for packaged products that embed affected Go components.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-61726 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
45Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-61726Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPgolang: net/url: Memory exhaustion in query parameter parsing in net/url
other:Red Hat severity ratingcvssV3_1
  • 2026-01-28T20:01:42.791Z: Reported to Red Hat.
  • 2026-01-28T19:30:31.215Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Go standard librarynet/urlnet/url, 0, 1.25.0unaffected
Weakness

CWE details

CWE-400CWE-770

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs