CVE-2026-50052: CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in The Vinyl Cache Project Vinyl Cache
In Vinyl Cache before 9.0.1 and Varnish Cache before 9.0.3, a deficiency in HTTP/2 request parsing can be exploited to launch a backend request desync attack (request smuggling), which in turn can be used for cache poisoning, authentication bypass, or possibly even information disclosure and manipulation. The attack vector only exists if HTTP/2 support is enabled by setting the feature parameter to contain +http2. HTTP/2 support is disabled by default.
AI Analysis
Technical Summary
Vinyl Cache versions prior to 9.0.1 contain a vulnerability in the HTTP/2 request parsing logic that allows an attacker to launch a backend request desynchronization attack, commonly known as HTTP request smuggling. This attack can be leveraged to poison the cache, bypass authentication mechanisms, or possibly disclose or manipulate information. The vulnerability only exists if the HTTP/2 feature is explicitly enabled via the feature parameter (+http2), which is disabled by default. No official remediation level or patch information is provided in the available data.
Potential Impact
Successful exploitation can result in cache poisoning, allowing an attacker to serve malicious or stale content to users. It may also enable authentication bypass, potentially granting unauthorized access, and could lead to information disclosure or manipulation. However, the attack vector requires HTTP/2 support to be enabled, which is not the default configuration, reducing the likelihood of exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, ensure HTTP/2 support is disabled (default setting) to mitigate the risk. Avoid enabling the +http2 feature parameter unless necessary and after confirming the presence of a fix.
CVE-2026-50052: CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in The Vinyl Cache Project Vinyl Cache
Description
In Vinyl Cache before 9.0.1 and Varnish Cache before 9.0.3, a deficiency in HTTP/2 request parsing can be exploited to launch a backend request desync attack (request smuggling), which in turn can be used for cache poisoning, authentication bypass, or possibly even information disclosure and manipulation. The attack vector only exists if HTTP/2 support is enabled by setting the feature parameter to contain +http2. HTTP/2 support is disabled by default.
CVSS v4.0
Score 2.3low
Affected software
pkg:github/vinyl-cache-project/vinyl-cacheRun 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
Vinyl Cache versions prior to 9.0.1 contain a vulnerability in the HTTP/2 request parsing logic that allows an attacker to launch a backend request desynchronization attack, commonly known as HTTP request smuggling. This attack can be leveraged to poison the cache, bypass authentication mechanisms, or possibly disclose or manipulate information. The vulnerability only exists if the HTTP/2 feature is explicitly enabled via the feature parameter (+http2), which is disabled by default. No official remediation level or patch information is provided in the available data.
Potential Impact
Successful exploitation can result in cache poisoning, allowing an attacker to serve malicious or stale content to users. It may also enable authentication bypass, potentially granting unauthorized access, and could lead to information disclosure or manipulation. However, the attack vector requires HTTP/2 support to be enabled, which is not the default configuration, reducing the likelihood of exploitation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, ensure HTTP/2 support is disabled (default setting) to mitigate the risk. Avoid enabling the +http2 feature parameter unless necessary and after confirming the presence of a fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-06-03T03:56:01.075Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1fbcb1e29bf47b50708570
Added to database: 06/03/2026, 05:33:37 UTC
Last enriched: 07/01/2026, 21:22:22 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 138
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.