CVE-2026-9604 JeecgBoot AiragModelController access control
Medium 5.3
Published
Updated
Check this codebase for CVE-2026-9604 and fix it if it is affected.
What it is: CVE-2026-9604 is a medium-severity vulnerability in JeecgBoot, published on 26 May 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9604 exists.
Affected product: JeecgBoot. 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-9604/ (Markdown: https://insights.sbomify.com/CVE-2026-9604/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-9604?
CVE-2026-9604 is a medium-severity vulnerability in JeecgBoot, published on 26 May 2026.
Official description
A vulnerability was detected in JeecgBoot up to 3.9.1. This vulnerability affects unknown code of the component AiragModelController. The manipulation of the argument list/queryById results in improper access controls. The attack can be executed remotely. The exploit is now public and may be used. Upgrading to version 3.9.2 is able to resolve this issue. The affected component should be upgraded.
Which versions are affected by CVE-2026-9604?
How do I fix CVE-2026-9604?
No fix has been published for CVE-2026-9604 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-9604 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9604 exists.
Sources
Also known as GHSA-32f8-xfvp-9m45.