VulnerabilityPublished 20 Feb 2026Updated 24 Feb 2026

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

Affects yeqifu warehouseSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score

5.3Medium

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.

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 20 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
yeqifuwarehouse	Affected =aaf29962ba407d22d991781de28796ee7b4670e4	Fixed in–

AI-suggested

To mitigate CVE-2026-2849, organizations should implement strict network-level access controls to limit exposure of the Cache Sync Handler endpoints to trusted users and systems only. Employ firewall rules or API gateways to restrict remote access to cache management functions. Conduct thorough access reviews and ensure that only authorized personnel or services have permissions to invoke cache operations. Implement monitoring and alerting on cache-related API calls to detect unusual or unauthorized activity promptly. If possible, apply application-layer authentication and authorization checks around the affected functions as a temporary workaround. Engage with the yeqifu project community to track any forthcoming patches or updates. Additionally, consider isolating the cache management service in a segmented network zone to reduce attack surface. Regularly audit logs and system behavior for anomalies related to cache manipulation. Finally, prepare incident response plans specific to cache integrity issues to minimize operational impact if exploitation occurs.

Description

A vulnerability has been found in yeqifu warehouse up to aaf29962ba407d22d991781de28796ee7b4670e4. Affected by this issue is the function deleteCache/removeAllCache/syncCache of the file dataset\repos\warehouse\src\main\java\com\yeqifu\sys\controller\CacheController.java of the component Cache Sync Handler. Such manipulation leads to improper access controls. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. 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's cache management functions can lead to unauthorized cache manipulation by remote attackers. This can result in data integrity compromise, where cache data is deleted or altered maliciously, potentially causing application errors, stale or incorrect data delivery, or denial of service if critical cache data is removed. Organizations relying on yeqifu warehouse for data storage or processing may experience operational disruptions, degraded performance, or data inconsistencies. Since the vulnerability requires only low-level privileges and no user interaction, attackers with minimal access could exploit it to escalate their impact. The lack of vendor response and patch increases exposure time, raising the risk of exploitation in production environments. This threat is particularly concerning for organizations with sensitive data or critical operations dependent on cache consistency and availability.

Summary

CVE-2026-2849 identifies an improper access control vulnerability in the yeqifu warehouse software, specifically within the Cache Sync Handler component's functions: deleteCache, removeAllCache, and syncCache. These functions reside in the CacheController.java file and are responsible for managing cache operations. Due to insufficient access control checks, remote attackers can invoke these functions to manipulate cache data without proper authorization. This can lead to unauthorized cache deletion or synchronization, potentially causing data integrity issues or denial of service conditions. The vulnerability is exploitable remotely without user interaction and requires only low-level privileges, increasing its risk profile. The yeqifu warehouse product follows a rolling release model, meaning continuous updates without fixed version numbers, which complicates identifying affected versions and deploying patches. Despite early reporting, the vendor has not issued a fix or official response. The CVSS 4.0 score is 5.3 (medium severity), reflecting the moderate impact on confidentiality, integrity, and availability, combined with ease of exploitation. No public exploits are currently known, but the vulnerability's public disclosure increases the risk of future exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 12:51 UTC

Technical details

References

Community reviews

Related threats