Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-75430 – Unauthenticated RCE – PowerJob Worker ≤5.1.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-75430 is a critical unauthenticated remote code execution vulnerability in PowerJob Worker. The Worker component exposes an HTTP endpoint that accepts an attacker-supplied download URL for a JAR file and loads it without any authentication, allowing full remote code execution on the Worker host. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: the Worker↔Server transport layer performs no token or signature authentication, so the request handler that processes container deployment requests fully trusts an attacker-supplied downloadURL parameter.
  • Trigger: an unauthenticated POST request to the Worker’s /worker/deployContainer HTTP endpoint (default transport port) with a JSON body specifying a downloadURL pointing to an attacker-hosted JAR.
  • Mechanism: the Worker downloads the JAR and loads it via a class loader combined with a Spring application context; context initialization instantiates beans and invokes their configured init-methods, which executes attacker-controlled code.
  • Attack vector: network, no authentication or user interaction required.
  • Impact: complete compromise of the Worker node, including exposure of job parameters/results and a potential foothold for pivoting into connected business systems.

Affected software

  • PowerJob Worker version 5.1.2 and reportedly earlier releases (the transport-layer authentication gap predates this release).

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: no official patched PowerJob release addressing this issue has been published at this time. Monitor the PowerJob project for a fixed version and upgrade as soon as one is available.
  • If no patch: restrict network access to the Worker transport port (do not expose it to the internet); place Workers behind a firewall/VPN limited to the PowerJob Server and trusted internal hosts; where possible, enforce mutual authentication between Server and Worker; block or allowlist outbound downloadURL destinations to prevent Workers from fetching JARs from untrusted, internet-reachable hosts.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: PowerJob

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge