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.
CVE-2026-65316
This medium-severity CVE scores 6.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(low)
- EPSS
- 30.7%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 21, 2026
References (3)
- disclosure@vulncheckhttps://github.com/xuxueli/xxl-job
- disclosure@vulncheckhttps://github.com/xuxueli/xxl-job/issues/3983
- disclosure@vulncheckhttps://www.vulncheck.com/advisories/xxl-job-cross-job-group-log-disclosure-via-missing-authorization-check-in-joblog-logdetailcat
Vendor Advisories for CVE-2026-65316(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 23:10 UTCEG score recompute
- 2026-07-21 21:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-65316?
When was CVE-2026-65316 disclosed?
Is CVE-2026-65316 actively exploited?
What is the CVSS score of CVE-2026-65316?
How do I remediate CVE-2026-65316?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65316
Is Your Infrastructure Affected by CVE-2026-65316?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.