Kubernetes
Multiple Products
Hot Chocolate is an open-source GraphQL server. Prior to versions 12.22.7, 13.9.16, 14.3.1, and 15.1.14, Hot Chocolate's recursive descent parser `Utf...
2026-04-18
Description
Hot Chocolate is an open-source GraphQL server. Prior to versions 12.22.7, 13.9.16, 14.3.1, and 15.1.14, Hot Chocolate's recursive descent parser `Utf8GraphQLParser` has no recursion depth limit. A crafted GraphQL document with deeply nested selection sets, object values, list values, or list types can trigger a `StackOverflowException` on payloads as small as 40 KB. Because `StackOverflowException` is uncatchable in .NET (since .NET 2.0), the entire worker process is terminated immediately. All in-flight HTTP requests, background `IHostedService` tasks, and open WebSocket subscriptions on that worker are dropped. The orchestrator (Kubernetes, IIS, etc.) must restart the process. This occurs before any validation rules run — `MaxExecutionDepth`, complexity analyzers, persisted query allow-lists, and custom `IDocumentValidatorRule` implementations cannot intercept the crash because `Utf8GraphQLParser.Parse` is invoked before validation. The `MaxAllowedFields=2048` limit does not help because the crashing payloads contain very few fields. The fix in versions 12.22.7, 13.9.16, 14.3.1, and 15.1.14 adds a `MaxAllowedRecursionDepth` option to `ParserOptions` with a safe default, and enforces it across all recursive parser methods (`ParseSelectionSet`, `ParseValueLiteral`, `ParseObject`, `ParseList`, `ParseTypeReference`, etc.). When the limit is exceeded, a catchable `SyntaxException` is thrown instead of overflowing the stack. There is no application-level workaround. `StackOverflowException` cannot be caught in .NET. The only mitigation is to upgrade to a patched version. Operators can reduce (but not eliminate) risk by limiting HTTP request body size at the reverse proxy or load balancer layer, though the smallest crashing payload (40 KB) is well below most default body size limits and is highly compressible (~few hundred bytes via gzip).
AI Analyst Comment
Remediation
Update Kubernetes Multiple Products to the latest version. Monitor for exploitation attempts and review access logs.
---METADATA---
VENDOR: Hackage
PRODUCT: hackage-server
AFFECTED_VERSIONS: 0.1 and later
CONFIDENCE: high
MISSING: patch
---END_METADATA---
Description Summary:
The hackage-server application lacks Cross-Site Request Forgery (CSRF) protection, allowing unauthorized actions such as package uploads or account creation via malicious scripts on foreign sites.
Executive Summary:
The hackage-server application is vulnerable to Cross-Site Request Forgery (CSRF), which could allow remote attackers to perform unauthorized administrative actions or modify user accounts.
Vulnerability Details
CVE-ID: CVE-2026-40471
Affected Software: Hackage hackage-server
Affected Versions: 0.1 and later
Vulnerability: This is a Cross-Site Request Forgery (CWE-352) vulnerability. The application fails to validate requests, allowing an attacker to trigger actions on behalf of an authenticated user or, in some cases, perform unauthenticated actions like account creation.
Business Impact
The lack of CSRF protection poses a significant risk to the integrity and availability of the package repository. A successful exploit could lead to unauthorized code execution through malicious package uploads or the compromise of administrative functions, resulting in severe reputational damage and supply chain risk. With a CVSS score of 9.6, this vulnerability is critical due to the potential for total impact on system confidentiality and integrity.
Remediation Plan
Immediate Action: Review the official OSV advisory (HSEC-2026-0002) for specific security guidance or configuration changes, as a direct patch version may not be explicitly listed.
Proactive Monitoring: Monitor server logs for suspicious POST requests originating from unexpected referrers or unusual patterns of administrative activity.
Compensating Controls: Implement strict SameSite cookie attributes and consider deploying a Web Application Firewall (WAF) to inspect and block suspicious cross-origin requests.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of April 23, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherently dangerous because it leverages the trust a server has in a user's browser, making it a high-priority target for automated cross-site attacks.
Analyst Recommendation
Given the critical CVSS severity, administrators should prioritize implementing site-wide CSRF protections immediately. If a software update is not yet available, verify that your deployment configuration follows the latest security hardening guidelines provided by the vendor to minimize the attack surface.