CVE-2026-55149: CWE-789: Memory Allocation with Excessive Size Value in vouch vouch-proxy
CVE-2026-55149 is a high-severity vulnerability in vouch-proxy prior to version 0.48.0. It involves improper handling of multipart cookie names, where an attacker can specify an excessively large part count that leads to a massive memory allocation attempt. This causes the Go runtime to run out of memory and crash the authentication proxy, resulting in denial of service. The issue is fixed in version 0.48.0.
AI Analysis
Technical Summary
Vouch-proxy versions before 0.48.0 contain a memory allocation vulnerability (CWE-789) in the cookie parsing logic. The vulnerable code parses the total part count from an attacker-controlled multipart cookie name and uses this value unchecked to allocate a slice. An attacker can craft a cookie name such as 'VouchCookie_1of10000000000' to trigger an allocation of approximately 160 GB, causing the Go runtime to crash due to out-of-memory conditions. This crash occurs before JWT validation and does not require a valid session or account. The vulnerability affects requests to /validate and /_external-auth-:id endpoints and allows an attacker to cause a denial of service by crashing the authentication proxy. The issue is resolved in vouch-proxy version 0.48.0.
Potential Impact
Successful exploitation causes the vouch-proxy authentication service to crash due to out-of-memory conditions, resulting in denial of service. There is no impact on confidentiality or integrity, as the vulnerability does not allow bypassing authentication or accessing sensitive data. The availability of the authentication proxy is affected until it is restarted or patched.
Mitigation Recommendations
Upgrade vouch-proxy to version 0.48.0 or later, where this vulnerability is fixed. No other mitigation is indicated or necessary as the fix addresses the root cause. Patch status is confirmed by the vendor advisory stating the issue is resolved in 0.48.0.
CVE-2026-55149: CWE-789: Memory Allocation with Excessive Size Value in vouch vouch-proxy
Description
CVE-2026-55149 is a high-severity vulnerability in vouch-proxy prior to version 0.48.0. It involves improper handling of multipart cookie names, where an attacker can specify an excessively large part count that leads to a massive memory allocation attempt. This causes the Go runtime to run out of memory and crash the authentication proxy, resulting in denial of service. The issue is fixed in version 0.48.0.
CVSS v3.1
Score 7.5high
Affected software
vouch
vouch-proxy
pkg:golang/github.com/vouch/vouch-proxyRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Vouch-proxy versions before 0.48.0 contain a memory allocation vulnerability (CWE-789) in the cookie parsing logic. The vulnerable code parses the total part count from an attacker-controlled multipart cookie name and uses this value unchecked to allocate a slice. An attacker can craft a cookie name such as 'VouchCookie_1of10000000000' to trigger an allocation of approximately 160 GB, causing the Go runtime to crash due to out-of-memory conditions. This crash occurs before JWT validation and does not require a valid session or account. The vulnerability affects requests to /validate and /_external-auth-:id endpoints and allows an attacker to cause a denial of service by crashing the authentication proxy. The issue is resolved in vouch-proxy version 0.48.0.
Potential Impact
Successful exploitation causes the vouch-proxy authentication service to crash due to out-of-memory conditions, resulting in denial of service. There is no impact on confidentiality or integrity, as the vulnerability does not allow bypassing authentication or accessing sensitive data. The availability of the authentication proxy is affected until it is restarted or patched.
Mitigation Recommendations
Upgrade vouch-proxy to version 0.48.0 or later, where this vulnerability is fixed. No other mitigation is indicated or necessary as the fix addresses the root cause. Patch status is confirmed by the vendor advisory stating the issue is resolved in 0.48.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T15:13:28.164Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa9769455bf5e2cf5196304
Added to database: 09/15/2026, 16:47:16 UTC
Last enriched: 09/15/2026, 17:01:56 UTC
Last updated: 09/15/2026, 17:23:37 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.