/

CVE-2026-75430

Severity:

CRITICAL RISK

(9.8)

Missing Authentication (CWE-306) in PowerJob Worker

CVE-2026-75430

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Remote Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

PowerJob Worker exposes the /worker/deployContainer HTTP endpoint without authentication on the default transport port. A remote attacker who can reach this endpoint may execute arbitrary code, making the issue critical when the worker is network-accessible.

Affected context

The vulnerability occurs in PowerJob Worker deployments where the default transport service exposes the /worker/deployContainer endpoint without an effective authentication requirement. Risk depends on network reachability, firewall and proxy controls, and whether the worker process has permissions that allow sensitive system or application actions.

Exploit preconditions

  • Attack surface: HTTP service exposed by the PowerJob Worker
  • Required access: Network connectivity to the worker's default transport port; valid credentials may not be required
  • Trigger point: A request to the unauthenticated /worker/deployContainer endpoint
  • Why exploitation is possible: The endpoint accepts deployment-related operations without first verifying the caller's identity and authorization

Why this happens

The underlying flaw is an externally reachable administrative or deployment endpoint that does not enforce authentication before processing requests. This maps to CWE-306: Missing Authentication for Critical Function, because a security-sensitive operation can be invoked without establishing the identity of the requester. The insecure pattern is exposing privileged functionality through a network interface while relying on network location or default deployment assumptions instead of explicit access control.

Potential impact

  • An attacker may execute arbitrary code in the PowerJob Worker process context.
  • The worker host or container could be compromised.
  • Application data and credentials accessible to the worker may be exposed.
  • An attacker could use the compromised worker for lateral movement or persistence.
  • Job execution integrity could be disrupted, potentially causing service outages or data manipulation.

General mitigation guidance

Mitigation generally focuses on ensuring that privileged worker operations are authenticated and authorized by default.

Common defensive patterns include:

  • Require strong authentication and explicit authorization for deployment and administrative endpoints.
  • Place worker transport services behind network controls that allow access only from trusted scheduler components.
  • Disable or remove deployment functionality when it is not required.
  • Use least-privilege service accounts, operating-system permissions, and container profiles for worker processes.
  • Avoid exposing internal worker ports directly to untrusted networks.
  • Apply secure-by-default service configuration and separate administrative interfaces from general application traffic.
  • Treat network isolation as defense in depth rather than a replacement for endpoint authentication.

How teams detect issues like this

Organizations can detect similar weaknesses through:

  • Static analysis and route reviews that identify sensitive HTTP handlers without authentication or authorization middleware.
  • Code review checks for deployment, execution, and administrative endpoints that lack identity and permission validation.
  • Dynamic testing that inventories exposed worker routes and verifies access-control behavior for unauthenticated requests.
  • Network policy enforcement that restricts worker transport ports to approved scheduler or control-plane sources.
  • Monitoring for unexpected requests to deployment endpoints and anomalous process creation by worker services.
  • Automated security review tools and API policy checks that flag publicly reachable critical operations without documented access controls.

Sources

SourceLink
gist.github.comgist.github.com/unpredictable21/fcb62d394db30525412c4b5b1efd0233
github.comgithub.com/PowerJob/PowerJob
github.comgithub.com/PowerJob/PowerJob/blob/master/SECURITY.md
github.comgithub.com/PowerJob/PowerJob/blob/master/powerjob-worker/src/main/java/tech/powerjob/worker/actors/WorkerActor.java
github.comgithub.com/PowerJob/PowerJob/blob/master/powerjob-worker/src/main/java/tech/powerjob/worker/container/OmsContainerFactory.java

Frequently asked

questions

Yes. Exploitation may be possible remotely when an attacker can reach the PowerJob Worker transport port and the endpoint remains unauthenticated.

Not necessarily. The reported condition is that the deployment endpoint does not require authentication, although network controls or upstream gateways may still restrict access.

Require authentication and authorization for the endpoint, restrict network exposure, and disable deployment functionality when it is unnecessary.

Maintain an inventory of sensitive routes, enforce authentication middleware by default, test unauthenticated access in CI and security assessments, and apply least-privilege network and process controls.

Find out what's already
exploitable in your codebase.