vouch-proxy has an Unbounded Multipart Cookie Allocation DoS
CVE-2026-55149GHSA-qqff-5854-px68
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/vouch/vouch-proxy 0.48.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/vouch/vouch-proxy
- Affected
- <= 0.47.2
- Fixed in
- 0.48.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-qqff-5854-px68 lists affected ranges: Go github.com/vouch/vouch-proxy >=0 <0.48.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6260 lists affected ranges: Go github.com/vouch/vouch-proxy >=0 <0.48.0 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-qqff-5854-px68 lists affected ranges: Go github.com/vouch/vouch-proxy >=0 <=0.47.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2026-55149: 0.72% estimated exploitation activity in the next 30 days; percentile 53.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Unbounded Multipart Cookie Allocation DoS in vouch-proxy Summary vouch-proxy v0.47.2 contains an unauthenticated remote denial-of-service vulnerability in its multipart cookie reassembly logic. The /validate endpoint parses the total cookie part count directly from the attacker-controlled cookie name (e.g., VouchCookie1of<N) and passes it without any bounds check to make([]string, N). A single HTTP request with N=10000000000 causes the Go runtime to attempt a ~160 GB heap allocation, triggering a fatal out-of-memory error that crashes the server process immediately. No authentication or prior session is required. Details The vulnerability exists in pkg/cookie/cookie.go. The Cookie() function iterates over all cookies in the request, identifies multipart cookies by the NofM suffix in their name, and initializes the reassembly slice on the first matching cookie: The value in xyArray[1] comes directly from the cookie name supplied by the client. There is no maximum value check, no…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-qqff-5854-px68
- Revision 2 · amended ·
Amended from osv record GO-2026-6260
- Revision 1 · created ·
Published from osv record GHSA-qqff-5854-px68
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-55149 Advisory: vouch-proxy has an Unbounded Multipart Cookie Allocation DoS IDs: CVE-2026-55149, GHSA-qqff-5854-px68 Record: https://patchnext.com/advisories/cve-2026-55149 (revision 3, source checked 26 Oct 2026, 15:29 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/vouch/vouch-proxy 0.48.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/vouch/vouch-proxy: affected <= 0.47.2; fixed in 0.48.0 ## Suggested inspection (read-only) - Go github.com/vouch/vouch-proxy: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/vouch/vouch-proxy. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-qqff-5854-px68 (OSV record GHSA-qqff-5854-px68 lists affected ranges: Go github.com/vouch/vouch-proxy >=0 <0.48.0 (fixed)) - Verified: https://osv.dev/vulnerability/GO-2026-6260 (OSV record GO-2026-6260 lists affected ranges: Go github.com/vouch/vouch-proxy >=0 <0.48.0 (fixed)) - Verified: https://github.com/advisories/GHSA-qqff-5854-px68 (GitHub-reviewed advisory GHSA-qqff-5854-px68 lists affected ranges: Go github.com/vouch/vouch-proxy >=0 <=0.47.2) Commands are suggestions: review each one before running it.
Loading voting…