CVE-2026-39825
Public on
Last Modified:
Description
A flaw was found in the net/http/httputil package, specifically within the ReverseProxy component. This vulnerability allows the ReverseProxy to forward query parameters that are not visible to Rewrite functions. This occurs because the ReverseProxy does not correctly consider the url.ParseQuery limit on the total number of query parameters. A remote attacker could exploit this to send hidden query parameters, potentially bypassing security policies or controls implemented by Rewrite functions, leading to information disclosure or unexpected behavior.
Statement
A flaw was found in Go's net/http/httputil package where ReverseProxy can forward query parameters that are hidden from Rewrite or Director functions. This occurs when the number of query parameters exceeds the url.ParseQuery limit (controlled by the GODEBUG setting urlmaxqueryparams). While Red Hat ships Go-based components across many products, exploitation requires that an application use ReverseProxy with a Rewrite or Director function that relies on query parameter inspection for security enforcement, which limits the practical impact of this vulnerability.
Mitigation
Increase the maximum number of query parameters allowed by setting the GODEBUG environment variable `urlmaxqueryparams` to a higher value (e.g., `GODEBUG=urlmaxqueryparams=20000`), or validate and enforce security controls on query parameters at the backend service rather than relying solely on the ReverseProxy's Rewrite or Director function for security filtering.
Additional information
- This content is not included.Bugzilla 2467823: net/http/httputil: golang: net/http/httputil: ReverseProxy forwards hidden query parameters, potentially bypassing security controls
- Content from cwe.mitre.org is not included.CWE-472: External Control of Assumed-Immutable Web Parameter
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2026-39825
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2026-39825
Content from go.dev is not included.https://go.dev/cl/770541
Content from go.dev is not included.https://go.dev/issue/78948
Content from pkg.go.dev is not included.https://pkg.go.dev/vuln/GO-2026-4976
Affected Packages and Issued Red Hat Security Errata
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | golang | Fixed | RHSA-2026:22120 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | golang | Fixed | RHSA-2026:49702 |
| Red Hat Enterprise Linux 8 | go-toolset:rhel8 | Fixed | RHSA-2026:22112 |
| Red Hat Enterprise Linux 9 | golang | Fixed | RHSA-2026:22121 |
| Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | golang | Fixed | This content is not included.RHSA-2026:61253 |
| Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions | golang | Fixed | RHSA-2026:57649 |
| Red Hat Enterprise Linux 9.6 Extended Update Support | golang | Fixed | RHSA-2026:49712 |
| multicluster engine for Kubernetes 2.11 | multicluster-engine/backplane-rhel9-operator | Fixed | This content is not included.RHSA-2026:57194 |
| multicluster engine for Kubernetes 2.11 | multicluster-engine/hypershift-addon-rhel9-operator | Fixed | This content is not included.RHSA-2026:57194 |
| multicluster engine for Kubernetes 2.11 | multicluster-engine/work-rhel9 | Fixed | This content is not included.RHSA-2026:57194 |
| No matching records found | |||
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| CVSS v3 Base Score | 6.5 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality Impact | Low | N/A | Low |
| Integrity Impact | Low | N/A | None |
| Availability Impact | None | N/A | None |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
cve.org CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
My product is listed as "Out of Support Scope". What does this mean?
Not sure what something means? Check out our Security Glossary.