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

Back
New CVE Detected

CVE-2026-75431 – Authentication Bypass leading to RCE – PowerJob Server ≤ 5.1.2

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-75431 is a critical use of a predictable/hard-coded cryptographic key vulnerability (CWE-321) in PowerJob Server version 5.1.2 and likely earlier. The JWT signing key used for HS256-based authentication on the web console and OpenAPI can be derived offline from publicly known values, letting a remote, unauthenticated attacker forge valid administrative tokens. This is rated CVSS 9.1 (Critical).

Technical details

  • Root cause: the HS256 JWT signing key is generated from a hard-coded constant combined with the MD5 hash of the default JDBC database URL, rather than a randomly generated and securely stored secret.
  • Trigger condition: default/unchanged JDBC URL configuration (as shipped in PowerJob’s reference docker-compose.yml and application-daily.properties) allows the signing key to be recomputed offline without any credentials.
  • Attack vector: network, no authentication or user interaction required; an attacker computes the key, forges a JWT (web console) or App Token (OpenAPI), and presents it to protected endpoints such as /namespace/list.
  • Impact: complete authentication bypass leading to admin-level access to the PowerJob console/API, with downstream potential for arbitrary code execution via job scheduling functionality.

Affected software

  • PowerJob Server version 5.1.2
  • Earlier PowerJob Server versions are also believed to be affected (deriving the same key logic)

Severity

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

Mitigation and recommended actions

  • Immediate: No official patched PowerJob release addressing this issue has been published as of this writing; monitor the PowerJob GitHub repository for a fixed release and upgrade as soon as one is available.
  • Workarounds:
    • Do not use the default/example JDBC URL from PowerJob’s reference configuration; use a unique, non-public database connection string.
    • Replace the JWT secret derivation logic with a randomly generated key stored securely (e.g., in an environment variable or secrets manager), separate from any database configuration value.
    • Restrict network exposure of the PowerJob web console (default port 7700) and OpenAPI endpoints to trusted internal networks only; do not expose them directly to the internet.
    • Rotate any credentials/tokens that may have been derived from or exposed alongside the default configuration.

How IONIX identifies potentially affected assets

IONIX matches the following signals 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