Quick answers
- Is CVE-2026-7306 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7306 being exploited in the wild.
- How severe is CVE-2026-7306?
- Medium severity, with a CVSS score of 5.6, published 28 April 2026.
- Which products and versions are affected?
- Xuxueli xxl-job up to 3.3.2.
- Is there a fix for CVE-2026-7306?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-7306 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-7306?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use of hard-coded cryptographic key (CWE-321) exists in the OpenAPI endpoint of XXL-JOB up to version 3.3.2. The OpenApiController.java component relies on the 'XXL-JOB-ACCESS-TOKEN' header for authorization but defaults to a publicly known value ('default_token'). Because the OpenAPI entrypoint explicitly disables SSO login, an unauthenticated remote attacker can use this default token to invoke privileged operations such as executor registration, registry removal, and task callbacks. While the attack is remote, it is classified as high complexity because it requires the target deployment to have retained the default configuration.
Affected products
- Xuxueli xxl-job up to 3.3.2
Timeline
- 2026-03-25: disclosed: Issue reported on GitHub repository
- 2026-04-28: advisory: NVD publication date