Quick answers
- Is CVE-2026-75431 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75431 being exploited in the wild.
- How severe is CVE-2026-75431?
- Critical severity, with a CVSS score of 9.1, published 4 September 2026.
- Which products and versions are affected?
- PowerJob Server 5.1.2 and likely earlier.
- Is there a fix for CVE-2026-75431?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-75431 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-75431?
- Check whether you run PowerJob Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in PowerJob Server's JWT authentication implementation (DefaultSecretProvider.java, JwtServiceImpl.java) which uses a predictable HMAC-SHA256 (HS256) signing key derived from a common database connection string. An attacker can offline compute the key using the default JDBC URL and forge valid admin tokens for any account, bypassing authentication entirely. No user interaction or prior authentication is required; the attack is purely network-based and affects default configurations. The PoC demonstrates successful token forgery that passes authentication on protected endpoints such as /namespace/list. Additionally, a separate OpenAPI token forgery vulnerability exists independently of admin password changes, further expanding the attack surface. No patch information is currently available from the advisory.
Affected products
- PowerJob PowerJob Server 5.1.2 and likely earlier
Timeline
- 2026-09-04: disclosed
- other: PoC code published on GitHub