Skip to main content
VulnerabilityPublished Updated

CVE-2025-11581: PowerJob · Missing Authorization

Affects PowerJobSource CVE Database V5

0

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PowerJobAffected
  • =5.1.0
  • =5.1.1
  • =5.1.2
Fixed in–

AI-suggested

  1. Immediate mitigation should focus on restricting network access to the /openApi/runJob endpoint by implementing firewall rules or API gateway policies to allow only trusted IP addresses or authenticated users.
  2. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized requests targeting this endpoint.
  3. Monitor logs and network traffic for unusual or unauthorized job execution attempts to enable rapid detection and response.
  4. If possible, upgrade to a patched version of PowerJob once available; until then, consider disabling the OpenAPIController or the /openApi/runJob endpoint if it is not essential for operations.
  5. Implement strict authentication and authorization mechanisms around job execution APIs, including API keys, OAuth tokens, or mutual TLS, to prevent unauthorized access.
  6. Conduct thorough security reviews of job definitions and submitted tasks to detect potentially malicious payloads.
  7. Educate DevOps and security teams about this vulnerability and ensure incident response plans include scenarios involving unauthorized job execution.
  8. Collaborate with PowerJob maintainers or community for timely updates and patches.

Description

A security vulnerability has been detected in PowerJob up to 5.1.2. This vulnerability affects unknown code of the file /openApi/runJob of the component OpenAPIController. Such manipulation leads to missing authorization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.

References

Community reviews

Loading reviews…