dbcve.org
InjectionWeakness · CWE-74

CVE-2026-5739

HIGH · 7.3 CVSS v3.1 Published 2026-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in PowerJob 5.1.0/5.1.1/5.1.2. The affected element is the function GroovyEvaluator.evaluate of the file /openApi/addWorkflowNode of the component OpenAPI Endpoint. The manipulation of the argument nodeParams results in code injection. The attack can be executed remotely. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A code injection vulnerability exists in PowerJob versions 5.1.0-5.1.2 within the GroovyEvaluator.evaluate function accessible via the /openApi/addWorkflowNode OpenAPI endpoint. The nodeParams parameter is not properly sanitized before evaluation, allowing remote attackers to inject and execute arbitrary Groovy code.

MitigationRestrict network access to OpenAPI endpoints, implement strict input validation/sanitization on nodeParams before Groovy evaluation, or deploy a WAF rule to block suspicious patterns until a vendor patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PowerJob installation and locate the application
    Check for PowerJob deployment files, services, or containers. Common paths include /opt/powerjob, installation directories, or Docker containers named 'powerjob'. Identify the process or service running PowerJob.
    Affected if PowerJob is present in the environment
  2. Identify the PowerJob version
    Check the JAR/WAR file names, pom.xml if source is present, or the application's startup logs for a version string (e.g., powerjob-x.x.x). Alternatively, query the /actuator/version or /api/version endpoint if exposed.
    Affected if The installed version is unknown or within any vulnerable release range (compare against any published affected versions)
  3. Verify the OpenAPI endpoint is accessible
    Attempt a GET request to http://<host>:<port>/openApi/addWorkflowNode or check the application routing configuration to confirm this endpoint exists and is routed to the PowerJob OpenAPI module.
    Affected if The /openApi/addWorkflowNode endpoint is accessible (no authentication or network restrictions found)
  4. Check if nodeParams parameter is processed by GroovyEvaluator
    Review application logs, debug traces, or code references to 'GroovyEvaluator.evaluate' and confirm that it accepts and processes the nodeParams field from incoming requests to /openApi/addWorkflowNode.
    Affected if GroovyEvaluator processes nodeParams without visible sanitization or sandboxing in the request flow
  5. Verify lack of input validation or security sandbox on the endpoint
    Inspect the source code, configuration, or runtime behavior of /openApi/addWorkflowNode. Look for absence of input validation routines or Groovy security sandbox enforcement (e.g., GroovyShell.GROOVY_SAFE namespace restrictions).
    Affected if No input validation is applied to nodeParams and no Groovy security sandbox is configured

The environment is affected if PowerJob is running with the /openApi/addWorkflowNode endpoint exposed and the nodeParams argument is processed by GroovyEvaluator without sanitization or a security sandbox.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to OpenAPI endpoints, implement strict input validation/sanitization on nodeParams before Groovy evaluation, or deploy a WAF rule to block suspicious patterns until a vendor patch is available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5739 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data