# CVE-2026-65316: xxl-job Cross-Job-Group Log Disclosure via Missing Authorization Check in /joblog/logDetailCat

> Authenticated users can read execution logs from unauthorized job groups by enumerating log IDs, exposing sensitive data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 21 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-7359-rm9q-rghc

## What is CVE-2026-65316?

CVE-2026-65316 is a high-severity missing authorization vulnerability in xuxueli xxl-job, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

XXL-Job version 2.4.2 contains an insecure direct object reference vulnerability that allows authenticated users to read execution log content from job groups they are not authorized to access by supplying arbitrary sequential log IDs to the logDetailCat endpoint. Attackers can enumerate log records across all job groups by calling the logDetailCat endpoint with incremented logId parameter values, bypassing the permission check present in the sibling logDetailPage endpoint, and retrieve sensitive log content from restricted job groups.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-65316 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65316 is a high-severity missing authorization vulnerability in xuxueli xxl-job, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65316 in the wild and no public exploit code.

Affected product: xuxueli xxl-job. 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-65316/ (Markdown: https://insights.sbomify.com/CVE-2026-65316/index.md)
```

## Sources

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

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