CVE-2026-1197VulnerabilityPublished 20 Jan 2026Updated 25 Mar 2026

CVE-2026-1197: MineAdmin · Information Disclosure

Affects MineAdminSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low : upgrade to 3.0.0 or 2.0.0 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.0, 2.0.0, 1.0.0

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade MineAdmin to 3.0.0 or 2.0.0; sourbyte05/MineAdmin-Vulnerability to 3.0.0, 2.0.0 or 1.0.0.

Affected software

Product	Affected	Fixed in
MineAdmin	Affected =1.* =2.*	Fixed in–
GitHubsourbyte05/MineAdmin-Vulnerability`pkg:github/sourbyte05/MineAdmin-Vulnerability`Other threats	Affected <1.0.0 <2.0.0 <3.0.0	Fixed in 1.0.0 2.0.0 3.0.0
GitHubMineAdmin`pkg:github/MineAdmin`Other threats	Affected >=1.0.0 <2.0.0 >=2.0.0 <3.0.0	Fixed in 2.0.0 3.0.0

CPE configurations (1)

cpe:2.3:a:mineadmin:mineadmin:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of official patches or vendor response, organizations should implement compensating controls to mitigate this vulnerability. First, restrict network access to the MineAdmin management interface and specifically to the /system/downloadById endpoint using firewalls, VPNs, or IP whitelisting to limit exposure to trusted users only. Second, implement strict access controls and authentication mechanisms to ensure only authorized personnel can access MineAdmin features, minimizing the risk of low-privilege exploitation. Third, monitor logs and network traffic for unusual or repeated access attempts to the downloadById endpoint, which may indicate exploitation attempts. Fourth, consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious parameter manipulations targeting the ID argument. Fifth, conduct internal code reviews or penetration tests to identify and remediate similar input validation weaknesses in MineAdmin or related systems. Finally, maintain an incident response plan ready to address any detected exploitation and keep abreast of any future vendor updates or patches.

Description

A vulnerability was detected in MineAdmin 1.x/2.x. Affected by this vulnerability is an unknown functionality of the file /system/downloadById. Performing a manipulation of the argument ID results in information disclosure. The attack can be initiated remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-1197 is unauthorized information disclosure, which could lead to leakage of sensitive data stored or accessible via the /system/downloadById endpoint in MineAdmin. While the confidentiality impact is rated low, the exposure of internal data could facilitate further attacks such as social engineering, reconnaissance, or privilege escalation. The vulnerability does not affect integrity or availability, limiting the scope of damage. However, organizations relying on MineAdmin for administrative or operational functions may face risks related to data privacy compliance and potential reputational damage if sensitive information is leaked. The high complexity of exploitation and low privileges required mean that only skilled attackers with some access could exploit this, reducing the likelihood of widespread attacks. The lack of vendor response and patches increases the window of exposure. Overall, the threat is moderate but should not be ignored, especially in environments where MineAdmin is critical and contains sensitive information.

References

Community reviews

Loading reviews…