# CVE-2026-5616: JeecgBoot AI Chat JeecgBizToolsProvider.java missing authentication

> Remote attackers can bypass authentication in the JeecgBoot AI Chat module due to missing access controls in the provider implementation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-52xr-h9vp-pxcj

## What is CVE-2026-5616?

CVE-2026-5616 is a medium-severity missing authorization vulnerability in JeecgBoot, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been detected in JeecgBoot 3.9.0/3.9.1. The impacted element is an unknown function of the file jeecg-boot/jeecg-module-system/jeecg-system-biz/src/main/java/org/jeecg/modules/airag/JeecgBizToolsProvider.java of the component AI Chat Module. Such manipulation leads to missing authentication. The attack can be executed remotely. The name of the patch is b7c9aeba7aefda9e008ea8fe4fc3daf08d0c5b39/2c1cc88b8d983868df8c520a343d6ff4369d9e59. It is best practice to apply a patch to resolve this issue. The project fixed the issue with a commit which shall be part of the next official release.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-5616 being exploited?

There is no known exploitation of CVE-2026-5616 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5616 is a medium-severity missing authorization vulnerability in JeecgBoot, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5616 in the wild and no public exploit code.

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-5616/ (Markdown: https://insights.sbomify.com/CVE-2026-5616/index.md)
```

## Sources

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

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