LiveActive security incident?Get immediate response
CVE Record

CVE-2026-75430: PowerJob Worker version 5.1.2 (and likely earlier versions) exposes the /worker/deployContainer HTTP endpoi...

PowerJob Worker version 5.1.2 (and likely earlier versions) exposes the /worker/deployContainer HTTP endpoint without authentication on the default transport port. This allows a remote attacker to execute arbitrary code.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

PowerJob Worker 5.1.2 exposes a management endpoint without authentication on its default transport port. An attacker who can reach that endpoint could run arbitrary code on the worker, potentially compromising its data, jobs, credentials, and connected systems. Earlier versions may also be vulnerable, but the supplied evidence does not confirm their exact range.

Executive priority

Treat reachable PowerJob Worker 5.1.2 systems as an immediate remediation priority because compromise requires no account or user action. First remove untrusted network access, then confirm vendor-supported remediation. Investigate endpoint access logs where exposure existed, while avoiding claims of compromise without evidence.

Technical view

CVE-2026-75430 is a missing-authentication flaw (CWE-306) affecting the /worker/deployContainer endpoint. The CVSS 3.1 score is 9.8: network-accessible, low complexity, requiring neither privileges nor user interaction, with high confidentiality, integrity, and availability impact. Version 5.1.2 is identified; earlier versions are only described as likely affected.

Likely exposure

Highest risk applies to PowerJob Worker 5.1.2 instances whose default transport port is reachable from untrusted networks. Internally reachable workers remain exposed to compromised hosts or malicious insiders. The supplied record lacks confirmed CPEs and a definitive earlier-version boundary, so inventory findings require vendor confirmation.

Exploitation context

The supplied record describes unauthenticated remote code execution, but it is not listed as a CISA KEV and the bundle provides no verified evidence of active exploitation. A referenced public gist may contain research material; its contents and reliability are not established in the supplied evidence.

Researcher notes

The affected-version statement is incomplete: 5.1.2 is explicit, while earlier releases are speculative. No CPEs, fixed version, patch, or vendor-confirmed workaround appear in the bundle. Code references identify WorkerActor and OmsContainerFactory as relevant review points. Validate authentication boundaries and exposure without executing container deployment or arbitrary code.

Mitigation direction

  • Restrict the worker transport port to explicitly trusted PowerJob components and management networks.
  • Block public and unnecessary cross-segment access to /worker/deployContainer.
  • Isolate affected workers and limit their access to credentials, data stores, and downstream systems.
  • Check PowerJob security guidance for a corrected release or vendor-approved mitigation.
  • Prioritize replacement or upgrading once the vendor confirms a fixed version.

Validation and detection

  • Inventory PowerJob Worker deployments and identify version 5.1.2 and earlier releases.
  • Verify whether each worker transport port is reachable from untrusted networks or network segments.
  • Confirm access controls deny unauthenticated requests to /worker/deployContainer without invoking deployment behavior.
  • Review proxy, firewall, and application logs for unexpected requests to the affected endpoint.
  • After remediation, revalidate network restrictions and endpoint authentication using non-destructive checks.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-75430 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N3.95.9mitre

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-75430Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.