CVE-2026-25203: Samsung Electronics MagicINFO 9 Server · Incorrect Default Permissions
Affects Samsung Electronics MagicINFO 9 ServerSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Apr 2026
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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Samsung ElectronicsMagicINFO 9 Server | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, restrict local access to trusted users only and monitor for suspicious activity. Avoid running the MagicINFO 9 Server on systems where untrusted users have local access. Apply the vendor's patch promptly once it becomes available.
Description
CVE-2026-25203 is a local privilege escalation vulnerability in Samsung MagicINFO 9 Server versions earlier than 21.1091.1. The issue arises from incorrect default permissions, which could allow a local attacker with limited privileges to escalate their access rights. The vulnerability has a high severity rating with a CVSS score of 7.8, indicating significant potential impact on confidentiality, integrity, and availability. There is no vendor-provided patch or official remediation guidance available at this time. No known exploits in the wild have been reported. Users of affected versions should monitor vendor advisories for updates and apply patches once available.