Rate-limit bypass via fail-open cookie parsing
Published Sep 16, 2026 · Updated Sep 17, 2026
Fail-open parsing in Higress before 2.2.4 allows remote attackers to bypass AI token rate limits via malformed Cookie headers. ExtractCookieValueByKey indexes a missing cookie value without checking the split length; panic recovery returns ActionContinue instead of rejecting the request. Exposure requires cookie-keyed rate limiting and a matching cookie name, allowing backend calls beyond configured thresholds rather than crashing the gateway.
Summary
What happened
Fail-open parsing in Higress before 2.2.4 allows remote attackers to bypass AI token rate limits via malformed Cookie headers. ExtractCookieValueByKey indexes a missing cookie value without checking the split length; panic recovery returns ActionContinue instead of rejecting the request. Exposure requires cookie-keyed rate limiting and a matching cookie name, allowing backend calls beyond configured thresholds rather than crashing the gateway.
The record
- CVE
- CVE-2026-92790
- Published
- Sep 16, 2026
- Updated
- Sep 17, 2026
- Vendor
- Higress
- Product
- Higress
- Classifications
- CWE-703
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.2.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Upstream issue rate-limit bypass proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us