VulnerabilityPublished 7 Feb 2026Updated 23 Feb 2026

CVE-2026-2075: yeqifu warehouse · Improper Access Controls

Affects yeqifu warehouseSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% 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:L/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: 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: 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: 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 7 Feb 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

Affected software

Product	Affected	Fixed in
yeqifuwarehouse	Affected =aaf29962ba407d22d991781de28796ee7b4670e4	Fixed in–

AI-suggested

Immediately restrict network access to the yeqifu warehouse RoleController endpoints, especially those handling role permission changes, using firewalls or network segmentation.
Implement strict access control policies at the application and infrastructure level to limit who can invoke role permission management functions.
Monitor logs and audit trails for unusual or unauthorized attempts to modify role permissions or access the RoleController component.
Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the saveRolePermission function.
Engage with the yeqifu vendor or community to obtain patches or updates as soon as they become available, given the rolling release model.
Consider deploying runtime application self-protection (RASP) tools to detect and prevent exploitation attempts in real-time.
Conduct a thorough review of existing role permissions to ensure no excessive privileges exist that could be abused if the vulnerability is exploited.
Educate internal teams about this vulnerability and the importance of monitoring for related attack indicators.
If possible, isolate the yeqifu warehouse deployment from public internet exposure until a patch is applied.
Prepare incident response plans to quickly address any exploitation attempts.

Description

A security flaw has been discovered in yeqifu warehouse up to aaf29962ba407d22d991781de28796ee7b4670e4. Affected is the function saveRolePermission of the file dataset\repos\warehouse\src\main\java\com\yeqifu\sys\controller\RoleController.java of the component Role-Permission Binding Handler. The manipulation results in improper access controls. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The improper access control vulnerability in yeqifu warehouse can lead to unauthorized modification of role permissions, enabling attackers to escalate privileges or alter access rights within the system. This can compromise the confidentiality and integrity of sensitive data managed by the warehouse application. Attackers exploiting this flaw remotely can gain unauthorized control over role assignments, potentially leading to further lateral movement within an organization's infrastructure. The availability impact is limited but could occur if attackers disrupt role management functionality. Given the role of access control in securing enterprise applications, exploitation could facilitate data breaches, unauthorized data manipulation, or disruption of business processes. Organizations relying on yeqifu warehouse for critical operations or sensitive data management face increased risk of insider-like attacks or external compromise. The public release of exploit code heightens the urgency for mitigation, as opportunistic attackers may leverage this vulnerability before patches are available.

Summary

CVE-2026-2075 is a security vulnerability identified in the yeqifu warehouse software, specifically within the Role-Permission Binding Handler component. The vulnerability resides in the saveRolePermission function located in the RoleController.java file. Due to improper access control implementation, an attacker can remotely exploit this flaw without requiring authentication or user interaction. The vulnerability allows manipulation of role permissions, which can lead to unauthorized privilege escalation or unauthorized modification of access rights within the system. The product's rolling release model complicates identification of fixed versions, and as of the publication date, the vendor has not responded to the issue report. The CVSS 4.0 base score is 5.3 (medium severity), reflecting the ease of remote exploitation (attack vector network, low attack complexity), no authentication required, and limited impact on confidentiality, integrity, and availability. Although no known exploits in the wild have been reported, the public availability of exploit code increases the risk of attacks. The vulnerability affects all versions up to commit aaf29962ba407d22d991781de28796ee7b4670e4. Organizations using yeqifu warehouse should consider this vulnerability a significant risk to their access control mechanisms and take immediate action to mitigate potential exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 22:12 UTC

Technical details

References

Community reviews

Related threats