CVE-2026-118984: OmniRoute 3.8.0 before 3.8.52 Unverified Password Change via /api/settings/require-login
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
OmniRoute 3.8.0 before 3.8.52 contains an unverified password change vulnerability that allows holders of manage- or admin-scoped API keys or oma_ access tokens to change the management password without the current password. Attackers can send POST requests to /api/settings/require-login to lock out the operator, take over dashboard login, or disable the login requirement entirely.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-29).
Weakness: Unverified Password Change
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing high privileges and no user interaction. Impact: confidentiality none, integrity high, availability low. CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 5 references on Exploit Observer
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| cheaper-inference OmniRoute | from 3.8.0 before 3.8.52 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 3.8.52.
Vendor guidance:
- Pull Request #16897 (patch, issue-tracking)
- Patch Commit (patch)
- OmniRoute v3.8.52 Release Notes (release-notes)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-118984 OmniRoute - Unverified Management Password Change via require-login. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-118984 OmniRoute - Unverified Management Password Change via require-login"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/settings/require-login"; nocase; fast_pattern; http.request_body; content:"password"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-118984; reference:url,https://www.exploit.observer/?keyword=CVE-2026-118984&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=omniroute&match=exact; sid:1104604; rev:1;)
CVE-2026-118984.rules on GitHub
References
Vendor advisories and patches
- Pull Request #16897 (patch, issue-tracking)
- Patch Commit (patch)
- OmniRoute v3.8.52 Release Notes (release-notes)
Technical analysis and advisories
- https://github.com/cheaper-inference/OmniRoute/blob/c1e30b7676975feb298b49eff6ff58923c04b89e/src/app/api/settings/require-login/route.ts#L90-L130 (technical-description)
- https://github.com/cheaper-inference/OmniRoute/blob/c1e30b7676975feb298b49eff6ff58923c04b89e/src/app/api/settings/route.ts#L374-L422 (technical-description)
- VulnCheck Advisory: OmniRoute 3.8.0 before 3.8.52 Unverified Password Change via /api/settings/require-login (third-party-advisory)
Other references
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
