VulnerabilityPublished 22 Feb 2026

CVE-2026-2957: qinming99 dst-admin · Denial of Service

Affects qinming99 dst-adminSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
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: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
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: None: There is no loss of confidentiality within 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 22 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
qinming99dst-admin	Affected 1.0 – 1.5.0 6 affected builds	Fixed in–

AI-suggested

Since no official patches or updates have been released by the vendor, organizations should implement the following specific mitigation strategies: 1) Restrict network access to the dst-admin application, limiting exposure to trusted IP addresses and internal networks only. 2) Enforce strict access controls and monitor user privileges to ensure that only authorized personnel with necessary low-level privileges can access backup management functions. 3) Implement application-layer firewalls or web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the deleteBackup function or related endpoints. 4) Monitor application logs and network traffic for unusual activity or repeated requests that could indicate exploitation attempts. 5) Consider deploying rate limiting on backup deletion endpoints to reduce the risk of DoS through repeated triggering. 6) Prepare incident response plans focused on backup service disruptions, including alternative backup management workflows. 7) Evaluate the feasibility of isolating the dst-admin service in a segmented environment to contain potential impacts. 8) Stay alert for vendor updates or community patches and apply them promptly once available. These targeted measures go beyond generic advice by focusing on access restriction, monitoring, and traffic filtering specific to the vulnerable function.

Description

A weakness has been identified in qinming99 dst-admin up to 1.5.0. This impacts the function deleteBackup of the file src/main/java/com/tugos/dst/admin/controller/BackupController.java of the component File Handler. This manipulation causes denial of service. The attack may be initiated remotely. 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 primary impact of CVE-2026-2957 is the disruption of backup management services within the qinming99 dst-admin application, leading to denial of service conditions. Organizations relying on dst-admin for backup operations may experience service outages, preventing them from deleting backups or managing backup data effectively. This can result in operational downtime, delayed recovery processes, and increased risk during disaster recovery scenarios. Although the vulnerability does not compromise data confidentiality or integrity, the loss of availability can have significant business implications, especially for organizations with strict backup retention policies or regulatory requirements. The public availability of exploit code increases the risk of automated attacks or opportunistic exploitation, potentially affecting multiple organizations simultaneously. The lack of vendor response and patches prolongs exposure, forcing organizations to rely on compensating controls. The scope is limited to dst-admin users, but given the critical nature of backup management, the impact on affected organizations can be moderate to high in operational terms.

Summary

CVE-2026-2957 is a denial of service (DoS) vulnerability identified in the qinming99 dst-admin product, specifically affecting versions 1.0 through 1.5.0. The vulnerability resides in the deleteBackup function of the BackupController.java source file, which is part of the File Handler component responsible for managing backup deletions. The flaw allows an attacker to remotely manipulate this function, causing the application to enter a denial of service state, rendering backup management functionalities unavailable. The vulnerability can be exploited without user interaction and requires only low-level privileges, making it accessible to a wider range of attackers with some access to the system. The vendor was notified early but has not issued any patches or responses, and the exploit code has been publicly disclosed, increasing the likelihood of exploitation attempts. The CVSS 4.0 base score is 5.3 (medium), reflecting the moderate impact on availability and the ease of remote exploitation without authentication. The vulnerability does not affect confidentiality or integrity directly but can disrupt critical backup operations, potentially impacting business continuity. No mitigations or patches have been officially released, leaving organizations dependent on alternative protective measures. The vulnerability is classified as a medium severity DoS issue with a scope limited to the dst-admin application and its backup management functionality.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Mar 2026, 06:35 UTC

Technical details

References

Community reviews

Related threats