# CVE-2026-108899: tobychui zoraxy Path Exception Matcher authProviders.go handleBasicAuth improper authorization

> Attackers can bypass authentication in zoraxy reverse proxy by manipulating path prefixes, allowing unauthorized access to protected resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-6qcv-qc7g-33wv

## What is CVE-2026-108899?

CVE-2026-108899 is a medium-severity missing authorization vulnerability in tobychui zoraxy, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in tobychui zoraxy up to 3.3.4. This impacts the function handleBasicAuth of the file mod/dynamicproxy/authProviders.go of the component Path Exception Matcher. This manipulation of the argument PathPrefix causes improper authorization. It is possible to initiate the attack remotely. The exploit has been published and may be used. Upgrading to version 3.3.5-rc1 will fix this issue. Patch name: 37cd0f27b17cd15cfa4af409bfec943146f5fdfe. Upgrading the affected component is advised.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-108899 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108899 is a medium-severity missing authorization vulnerability in tobychui zoraxy, published on 12 Oct 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-108899 exists.

Affected product: tobychui zoraxy. 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-108899/ (Markdown: https://insights.sbomify.com/CVE-2026-108899/index.md)
```

## Sources

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

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