CVE-2026-2849

5.4 MEDIUM

📋 TL;DR

This vulnerability in yeqifu warehouse allows improper access controls in cache management functions, potentially enabling unauthorized cache manipulation. Attackers can exploit this remotely to delete or sync cache data without proper authentication. All deployments using affected commits are vulnerable.

💻 Affected Systems

Products:
  • yeqifu warehouse
Versions: All versions up to commit aaf29962ba407d22d991781de28796ee7b4670e4
Operating Systems: Any OS running Java applications
Default Config Vulnerable: ⚠️ Yes
Notes: Rolling release model means no specific version numbers - all deployments using affected code commits are vulnerable

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete cache data loss or corruption leading to application instability, denial of service, or data integrity issues

🟠

Likely Case

Unauthorized cache manipulation causing application performance degradation or inconsistent data presentation

🟢

If Mitigated

Minimal impact with proper authentication and authorization controls in place

🌐 Internet-Facing: HIGH - Attack can be launched remotely and exploit is publicly disclosed
🏢 Internal Only: MEDIUM - Internal attackers could exploit but requires network access

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploit disclosed in GitHub issue #60, requires remote access to cache management endpoints

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch available. Monitor GitHub repository for updates or consider forking and implementing proper access controls.

🔧 Temporary Workarounds

Network Access Restriction

linux

Restrict access to cache management endpoints using firewall rules or network segmentation

iptables -A INPUT -p tcp --dport [APP_PORT] -s [TRUSTED_NETWORK] -j ACCEPT
iptables -A INPUT -p tcp --dport [APP_PORT] -j DROP

Authentication Enforcement

all

Implement authentication middleware for all cache management endpoints

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block unauthorized cache management requests
  • Monitor and alert on suspicious cache manipulation activities

🔍 How to Verify

Check if Vulnerable:

Check if your deployment uses commit aaf29962ba407d22d991781de28796ee7b4670e4 or earlier: git log --oneline | grep aaf29962ba407d22d991781de28796ee7b4670e4

Check Version:

git rev-parse HEAD

Verify Fix Applied:

Test cache management endpoints with unauthenticated requests - they should return 401/403 errors

📡 Detection & Monitoring

Log Indicators:

  • Unauthorized access attempts to /cache endpoints
  • Cache deletion/sync operations from unexpected IPs
  • 401/403 errors followed by successful cache operations

Network Indicators:

  • HTTP requests to /deleteCache, /removeAllCache, /syncCache endpoints without authentication headers
  • Unusual cache-related traffic patterns

SIEM Query:

source="application.logs" AND (uri_path="/deleteCache" OR uri_path="/removeAllCache" OR uri_path="/syncCache") AND NOT (user!="anonymous" OR auth_success="true")

🔗 References

📤 Share & Export