Is CVE-2026-5739 exploited in the wild?

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

How severe is CVE-2026-5739?

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-5739?

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

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

Am I affected by CVE-2026-5739?

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-5739: PowerJob Groovy code injection in OpenAPI Endpoint

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

PowerJob, an enterprise job scheduling middleware, contains a security flaw that allows remote attackers to execute arbitrary code on the server. By sending specially crafted requests to the system's open API, an attacker can bypass authentication and run malicious scripts. This could lead to a complete takeover of the server, unauthorized access to sensitive data, and disruption of scheduled business operations.

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

Quick answers

Is CVE-2026-5739 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5739 being exploited in the wild.
How severe is CVE-2026-5739?: 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-5739?: 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-5739 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-5739?: 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 remote code execution (RCE) vulnerability exists in PowerJob versions 5.1.0, 5.1.1, and 5.1.2 due to a combination of two flaws. First, the OpenAPI endpoint (/openApi/*) is unauthenticated by default because the 'oms.auth.openapi.enable' configuration defaults to false. Second, the 'GroovyEvaluator.evaluate' function lacks a sandbox, using 'ScriptEngine.eval()' to process the 'nodeParams' argument from 'addWorkflowNode' requests. An attacker can chain these flaws by creating a workflow with a 'DECISION' node containing a malicious Groovy script and then triggering that workflow via 'runWorkflow'. This results in arbitrary code execution within the Server JVM context. As of the advisory date, no official patch has been released, though workarounds include enabling OpenAPI authentication and implementing Groovy sandboxing.

Affected products

PowerJob PowerJob 5.1.0, 5.1.1, 5.1.2

Identifiers

CVE-2026-5739
GHSA-wpwf-v25w-54g3

Timeline

2026-03-24: disclosed: Issue reported on GitHub repository
2026-04-07: advisory: VulDB and NVD publication

References

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