# CVE-2026-2075: yeqifu warehouse Role-Permission Binding RoleController.java saveRolePermission access control

> Remote attackers can bypass access controls in the Role-Permission Binding handler to modify role permissions, potentially escalating privileges.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-w9hx-x484-j26w

## What is CVE-2026-2075?

CVE-2026-2075 is a medium-severity missing authorization vulnerability in yeqifu warehouse, published on 7 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-2075?

It affects 1 product.


Products: Yeqifu Warehouse.

## How do I fix CVE-2026-2075?

No fix has been published for CVE-2026-2075 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2075 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2075 exists.

## Other vulnerabilities in yeqifu warehouse

- [CVE-2026-2849](https://insights.sbomify.com/CVE-2026-2849/): yeqifu warehouse Cache Sync CacheController.java syncCache access control (medium 5.3)
- [CVE-2026-2850](https://insights.sbomify.com/CVE-2026-2850/): yeqifu warehouse Customer Endpoint CustomerController.java deleteCustomer access control (medium 5.3)
- [CVE-2026-2851](https://insights.sbomify.com/CVE-2026-2851/): yeqifu warehouse Inport Endpoint InportController.java deleteInport access control (medium 5.3)
- [CVE-2026-2852](https://insights.sbomify.com/CVE-2026-2852/): yeqifu warehouse Sales Endpoint SalesController.java deleteSales access control (medium 5.3)
- [CVE-2026-2076](https://insights.sbomify.com/CVE-2026-2076/): yeqifu warehouse User Management Endpoint UserController.java deleteUser improper authorization (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2075 and fix it if it is affected.

What it is: CVE-2026-2075 is a medium-severity missing authorization vulnerability in yeqifu warehouse, published on 7 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2075 exists.

Affected product: yeqifu warehouse. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2075/ (Markdown: https://insights.sbomify.com/CVE-2026-2075/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2075
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2075
- OSV: https://osv.dev/vulnerability/CVE-2026-2075

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2075/
Summaries are generated and may contain mistakes; the official description above is the record.