# CVE-2026-82630: PowerJob Transport Endpoint TestController.java MuConnectionManager.getOrCreateConnection server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in PowerJob's TestController to access internal resources or bypass security controls.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-787p-w8q7-9j73

## What is CVE-2026-82630?

CVE-2026-82630 is a medium-severity server-side request forgery vulnerability in PowerJob, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in PowerJob up to 5.1.2. Impacted is the function MuConnectionManager.getOrCreateConnection of the file powerjob-server/powerjob-server-starter/src/main/java/tech/powerjob/server/web/controller/TestController.java of the component Transport Endpoint. The manipulation leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-82630?


## How do I fix CVE-2026-82630?

No fix has been published for CVE-2026-82630 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82630 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82630 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82630 and fix it if it is affected.

What it is: CVE-2026-82630 is a medium-severity server-side request forgery vulnerability in PowerJob, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82630 exists.

Affected product: PowerJob. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82630/ (Markdown: https://insights.sbomify.com/CVE-2026-82630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82630
- OSV: https://osv.dev/vulnerability/CVE-2026-82630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82630/
Summaries are generated and may contain mistakes; the official description above is the record.