VulnerabilityPublished 20 Jan 2026Updated 25 Mar 2026

CVE-2026-1195: MineAdmin · Insufficient Verification of Data Authenticity

Affects MineAdminSource CVE Database V5

Public exploit available · CVSS 2.3 Low : upgrade to 3.0.0 or 2.0.0 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

2.3Low

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

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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: Low
Vulnerable system availability: Low
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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 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 <3.0.0	Fixed in 1.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. These include: 1) Restrict network access to MineAdmin's refresh endpoint (/system/refresh) using firewall rules or network segmentation to limit exposure to trusted sources only. 2) Monitor and log all token refresh requests for unusual patterns or anomalies that could indicate exploitation attempts. 3) Implement additional application-layer validation or integrity checks on JWT tokens if possible, such as verifying token signatures with updated cryptographic standards. 4) Enforce strict access controls and least privilege principles to reduce the likelihood that an attacker can gain the necessary privileges to exploit this vulnerability. 5) Regularly audit and update authentication mechanisms and consider alternative or supplemental authentication solutions if MineAdmin remains unpatched. 6) Stay alert for any future vendor advisories or community patches and apply them promptly. 7) Conduct penetration testing focused on token handling and refresh processes to identify potential exploitation vectors within the environment.

Description

A weakness has been identified in MineAdmin 1.x/2.x. This impacts the function refresh of the file /system/refresh of the component JWT Token Handler. This manipulation causes insufficient verification of data authenticity. It is possible to initiate the attack remotely. The attack is considered to have high complexity. The exploitability is said to be difficult. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The potential impact of CVE-2026-1195 is relatively limited due to the high complexity and low exploitability of the vulnerability, as well as the low CVSS score. However, if successfully exploited, it could allow an attacker to manipulate JWT token refresh operations, potentially leading to unauthorized access or privilege escalation within MineAdmin-managed environments. This could compromise session integrity and allow attackers to impersonate legitimate users or maintain persistent access. For organizations relying heavily on MineAdmin for critical authentication workflows, this could undermine trust in session management and lead to data exposure or unauthorized actions. The absence of vendor patches and public exploit availability increases the risk of future exploitation attempts. Nonetheless, the requirement for low privileges and no user interaction somewhat mitigates the threat, as attackers would need some initial access or foothold to leverage this vulnerability effectively.

Summary

CVE-2026-1195 identifies a security weakness in the MineAdmin software, specifically in versions 1.x and 2.x, within the JWT Token Handler component's refresh function located at /system/refresh. The vulnerability arises from insufficient verification of data authenticity during token refresh operations, which could allow a remote attacker to manipulate or forge JWT tokens. This manipulation could potentially lead to unauthorized actions or access if the token validation process is bypassed or weakened. The attack vector is network-based (AV:N), requiring low privileges (PR:L) but no user interaction (UI:N). The attack complexity is high (AC:H), indicating that exploitation requires significant effort or conditions. The vulnerability does not affect system confidentiality, integrity, or availability to a large extent, as reflected by the low CVSS 4.0 score of 2.3. No patches or vendor responses have been provided, and while a public exploit exists, there are no confirmed reports of exploitation in the wild. The lack of vendor response may delay remediation, increasing risk for users of affected versions. The vulnerability's impact is limited by the high complexity and low exploitability, but it remains a concern for organizations relying on MineAdmin for authentication and session management.

References

Community reviews

Loading reviews…