mihomo · Incorrect Access Control
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 13 Nov 2026, 20:29 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmetacubex/mihomopkg:github/metacubex/mihomoOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict access to authenticated users and monitor for suspicious access patterns to configuration files containing sensitive keys.
Description
mihomo version 1.19.11 contains an incorrect access control vulnerability that allows authenticated users with low-level privileges to read arbitrary files with elevated privileges by accessing an external control key stored in the configuration file.