CVE-2025-56499: Incorrect access control in mihomo v1.19.11 allows authenticated attackers with low-level privileges to read a

Routine

MEDIUM 6.5DOWNGRADE

CVE-2025-56499 is a medium-severity flaw (CVSS 6.5) affecting mihomo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Incorrect access control in mihomo v1.19.11 allows authenticated attackers with low-level privileges to read arbitrary files with elevated privileges via obtaining the external control key from the config file.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-284
Published	2025-11-18
Last modified	2026-07-29

Publisher (CNA): MITRE · Vendor: metacubex

Last updated 2026-07-29 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-11-18 19:15 UTCPublished CVE record published
2026-07-29 19:13 UTCUpdated Record last modified

metacubex mihomo DOWNGRADE

Affected: 1.19.11

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.19.11

1. Check installed version

apt-cache policy mihomo || rpm -q mihomo || mihomo --version

2. No fixed release: DOWNGRADE to a release before 1.19.11 (Debian / Ubuntu)

apt-cache madison mihomo sudo apt install mihomo=<VERSION_BEFORE_1.19.11> sudo apt-mark hold mihomo

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mihomo sudo dnf downgrade mihomo-<VERSION_BEFORE_1.19.11> sudo dnf versionlock add mihomo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-56499?

mihomo: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-56499 being exploited?

CVE-2025-56499 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-56499 affect?

CVE-2025-56499 affects mihomo. Severity is medium (CVSS 6.5). Incorrect access control in mihomo v1.19.11 allows authenticated attackers with low-level privileges to read arbitrary files with elevated privileges via obtaining the external control key from the config file.

How urgent is CVE-2025-56499?

Priority 34/100. Public exploit reference

References

← Back to latest CVEs