# CVE-2026-92790: Higress before 2.2.4 Rate Limit Bypass via Malformed Cookie Header

> Unauthenticated attackers can bypass AI token rate limiting by sending a malformed Cookie header, allowing them to exceed usage thresholds on costly model backends.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-467c-wf8v-3rh9

## What is CVE-2026-92790?

CVE-2026-92790 is a medium-severity vulnerability in higress-group higress, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Higress before 2.2.4 panics when processing a Cookie header segment without an equals sign, causing the plugin wrapper to recover and return a continue action that bypasses AI token rate limiting. Unauthenticated attackers can craft a malformed Cookie header to skip rate limit checks and exceed thresholds intended to restrict costly model backend calls.

Weakness: CWE-703 (Improper Check or Handling of Exceptional Conditions)

## Which versions are affected by CVE-2026-92790?


## How do I fix CVE-2026-92790?

No fix has been published for CVE-2026-92790 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92790 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92790 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92790 and fix it if it is affected.

What it is: CVE-2026-92790 is a medium-severity vulnerability in higress-group higress, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92790 exists.

Affected product: higress-group higress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92790/ (Markdown: https://insights.sbomify.com/CVE-2026-92790/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92790
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92790
- OSV: https://osv.dev/vulnerability/CVE-2026-92790

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92790/
Summaries are generated and may contain mistakes; the official description above is the record.