CVE-2026-25577
CookieError Handling Flaw in Emmett Request Causes DoS
Publication date: 2026-02-10
Last updated on: 2026-02-11
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| emmett | emmett | to 1.3.11 (inc) |
| emmett | emmett-core | to 1.3.11 (exc) |
| emmett | emmett-core | to 1.3.10 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-248 | An exception is thrown from a function, but it is not caught. |
| CWE-307 | The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Emmett framework versions prior to 1.3.11. Specifically, the cookies property in mmett_core.http.wrappers.Request does not properly handle CookieError exceptions when parsing malformed Cookie headers. Because of this, unauthenticated attackers can cause the application to throw HTTP 500 errors, leading to a denial of service condition.
How can this vulnerability impact me? :
The vulnerability allows unauthenticated attackers to trigger HTTP 500 errors by sending malformed Cookie headers. This results in denial of service, meaning legitimate users may be unable to access the affected application or service while it is disrupted.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade the Emmett framework to version 1.3.11 or later, where the issue with handling CookieError exceptions in the cookies property has been fixed.