CVE-2026-116634 | 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.
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.
- 🔗 github.com/cheaper-inference/OmniRoute/pull/17053
- 🔗 github.com/cheaper-inference/OmniRoute/commit/44a296…
- 🔗 github.com/cheaper-inference/OmniRoute/blob/c1e30b76…
- 🔗 github.com/cheaper-inference/OmniRoute/blob/c1e30b76…
- 🔗 github.com/cheaper-inference/OmniRoute/releases/tag/…
- 🔗 github.com/cheaper-inference/OmniRoute
- 🔗 www.vulncheck.com/advisories/omniroute-3.8.50-before-3.8.52…
Zero-Day & Vulnerability Intelligence Hub
Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
| Tier | CVEs | Anteil |
|---|---|---|
| ≥90 % | 743 | 0,2 % |
| ≥50 % | 3.224 | 0,8 % |
| ≥10 % | 22.067 | 5,8 % |
| <10 % | 354.695 | 93,2 % |
CVE-2026-116634 | 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.
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 GE