CVE-2026-75431
nicheHard-coded JWT signing key enables unauthenticated RCE in PowerJob Server
PowerJob Server 5.1.2 and likely earlier versions use a predictable (hard-coded) signing key for HS256-signed JWT authentication tokens (CWE-321), meaning every deployment that keeps the default key derives the same secret. Because the key is predictable, a remote, unauthenticated attacker can forge valid JWTs for arbitrary accounts and gain full access to the server without credentials or user interaction, which per the advisory leads to arbitrary code execution. Any deployment running PowerJob Server 5.1.2 or an earlier version is affected, with internet-exposed instances most directly at risk since no authentication is needed to exploit. No public proof-of-concept, CISA KEV listing, or confirmed in-the-wild exploitation is currently known; EPSS estimates a 0.8% probability of exploitation within the next 30 days.
What to do: Upgrade PowerJob Server to a patched release newer than 5.1.2 that randomizes the JWT signing key as soon as one is available; the advisory does not yet specify a fixed version number. As interim mitigation, restrict network access to PowerJob Server to trusted clients and, if the deployment allows overriding the JWT secret, replace it with a strong, randomly generated key. Review logs for unexpected successful authentications or unfamiliar task executions, since forged tokens may appear as legitimate logins.
| PowerJob Server | 5.1.2 and likely earlier versions |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
PowerJob Server version 5.1.2 (and likely earlier) uses a predictable JWT signing key for HS256-based authentication. This allows a remote attacker to execute arbitrary code.
- Weakness
- CWE-321
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
In the news0 stories
No ingested article mentions this CVE yet.