# CVE-2026-116634: OmniRoute 3.8.50 before 3.8.52 Missing Authentication via /api/sync/tokens


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-fqp9-jcg9-vhfv

## What is CVE-2026-116634?

CVE-2026-116634 is a high-severity vulnerability in cheaper-inference OmniRoute, published on 26 Oct 2026. 

### Official description

OmniRoute 3.8.50 before 3.8.52 contains a missing authentication vulnerability that allows unauthenticated attackers to issue sync tokens via POST /api/sync/tokens when requireLogin is disabled. Attackers can use the issued token against GET /api/sync/bundle to retrieve decrypted provider credentials and plaintext API keys, with tokens persisting after login is re-enabled.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-116634 being exploited?

There is no known exploitation of CVE-2026-116634 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116634 is a high-severity vulnerability in cheaper-inference OmniRoute, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116634 in the wild and no public exploit code.

Affected product: cheaper-inference OmniRoute. 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-116634/ (Markdown: https://insights.sbomify.com/CVE-2026-116634/index.md)
```

## Sources

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

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