Is CVE-2026-5736 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-5736 being exploited in the wild.

How severe is CVE-2026-5736?

High severity, with a CVSS score of 7.3, published 7 April 2026.

Which products and versions are affected?

tech.powerjob:powerjob-server-starter (Maven) ECOSYSTEM:introduced=5.1.0,last_affected=5.1.2; PowerJob 5.1.0, 5.1.1, 5.1.2.

Is there a fix for CVE-2026-5736?

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-5736 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-5736?

Check whether you run tech.powerjob:powerjob-server-starter (Maven) or PowerJob at an affected version. 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.

CVE-2026-5736: PowerJob SQL injection and RCE in detailPlus endpoint

CVE-2026-5736 · Severity: high · CVSS 7.3 · Published 2026-04-07

PowerJob, an enterprise job scheduling middleware, contains a security flaw in its instance detail endpoint. An unauthenticated attacker can exploit this to execute unauthorized database commands and potentially take full control of the server. This could lead to the theft of sensitive data, disruption of scheduled business tasks, or a complete system compromise.

Technologies: tech.powerjob:powerjob-server-starter (Maven), PowerJob. Vendors: Maven, PowerJob.

Quick answers

Is CVE-2026-5736 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5736 being exploited in the wild.
How severe is CVE-2026-5736?: High severity, with a CVSS score of 7.3, published 7 April 2026.
Which products and versions are affected?: tech.powerjob:powerjob-server-starter (Maven) ECOSYSTEM:introduced=5.1.0,last_affected=5.1.2; PowerJob 5.1.0, 5.1.1, 5.1.2.
Is there a fix for CVE-2026-5736?: 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-5736 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-5736?: Check whether you run tech.powerjob:powerjob-server-starter (Maven) or PowerJob at an affected version. 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 vulnerability exists in PowerJob versions 5.1.0 through 5.1.2 due to a combination of missing authorization and insufficient input validation. The 'detailPlus' endpoint in InstanceController.java lacks the @ApiPermission annotation, allowing unauthenticated access. Furthermore, the 'customQuery' parameter is directly concatenated into H2 SQL queries without sufficient blacklisting of dangerous keywords like 'RUNSCRIPT' or 'CALL'. An attacker can leverage this SQL injection to execute H2-specific commands, leading to remote code execution (RCE). A pull request (#1166) has been proposed to add the missing permission checks and expand the keyword blacklist, but a formal release may still be pending.

Affected products

PowerJob PowerJob 5.1.0, 5.1.1, 5.1.2

Identifiers

CVE-2026-5736
GHSA-4fp2-3xgg-jg4w

Timeline

2026-03-24: disclosed: Issue and Pull Request submitted to GitHub repository
2026-04-07: advisory: Initial advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.