LiveActive security incident?Get immediate response
CVE Record

CVE-2026-75431: PowerJob Server version 5.1.2 (and likely earlier) uses a predictable JWT signing key for HS256-based authe...

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

PowerJob Server 5.1.2, and possibly earlier releases, reportedly uses a predictable secret to authenticate users. A remote, unauthenticated attacker could potentially impersonate a trusted user and ultimately run arbitrary code on the server, threatening hosted workloads, credentials, and connected systems.

Executive priority

Treat internet-accessible or broadly reachable PowerJob Server deployments as an immediate remediation priority. Restrict exposure, determine the effective signing-key configuration, and obtain vendor-confirmed remediation. Investigate suspicious privileged or job-execution activity, but do not claim compromise solely from version presence.

Technical view

The reported weakness is a hard-coded or predictable cryptographic key (CWE-321) used to sign HS256 JWTs. Because HS256 verification depends on secrecy of the shared key, predictability may permit token forgery. The CVE states that exploitation can lead to remote code execution without privileges or user interaction.

Likely exposure

Highest risk applies to PowerJob Server 5.1.2 instances reachable from untrusted networks. Earlier versions may also be affected, but the supplied record does not establish an exact version range. Exposure also depends on whether deployments retain the predictable default signing-key behavior.

Exploitation context

The CVSS 3.1 score is 9.1, reflecting network access, low complexity, no required privileges, and high confidentiality and integrity impact. The supplied bundle does not show CISA KEV listing or otherwise confirm active exploitation. A public disclosure gist is referenced, but its evidentiary details were not supplied.

Researcher notes

The record attributes the issue to HS256 key predictability and claims an unauthenticated remote-code-execution outcome. However, the supplied affected-product data is blank, earlier-version impact is qualified as likely, and no fixed version or vendor mitigation is identified. Validate scope and the authorization-to-code-execution path against authoritative vendor updates.

Mitigation direction

  • Identify PowerJob Server deployments and restrict access from untrusted networks immediately.
  • Check PowerJob vendor guidance for a fixed release or supported configuration change.
  • Replace predictable JWT secrets with unique, cryptographically random values if vendor-supported.
  • Invalidate existing authentication tokens after changing the signing secret.
  • Monitor administrative and job-execution activity for unauthorized actions.

Validation and detection

  • Inventory deployed PowerJob Server versions and document externally reachable instances.
  • Review effective JWT configuration without recording or exposing secret values.
  • Confirm the signing secret is unique, non-default, and sufficiently random.
  • Verify old tokens become invalid after any approved secret rotation.
  • Review authentication, administration, and job-execution logs for anomalies.
Prepared
Confidence
medium
Sources
7

Public sources used

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 · low confidence lookup

CWE-321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-75431 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AC:L/AV:N/A:N/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
7Source 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.1CVSS 3.1CriticalCVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:N/S:U/UI:N3.95.2mitre

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AC:L/AV:N/A:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-321

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

CWE-321 · source CWE mapping

Use of Hard-coded Cryptographic Key

Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs