# CVE-2026-48592: Missing authorization check on save-job event handler in oban_web

> An authenticated read-only user can forge WebSocket events to overwrite job worker modules, leading to unauthorized code execution during job processing.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** EEF-CVE-2026-48592, GHSA-389x-rgxr-8m33

## What is CVE-2026-48592?

CVE-2026-48592 is a medium-severity missing authorization vulnerability in oban-bg oban_web, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in oban-bg oban_web ('Elixir.Oban.Web.Jobs.DetailComponent' modules) allows unauthorized job worker substitution.

The handle_event("save-job", ...) handler in 'Elixir.Oban.Web.Jobs.DetailComponent' does not perform an authorization check, unlike the sibling cancel, delete, and retry handlers which all verify the caller's privileges via can?/2. An authenticated user with :read_only access can push a forged save-job LiveView WebSocket event to overwrite a job's worker field with any other existing Oban.Worker module in the application. On the job's next execution attempt, Oban will invoke perform/1 on the attacker-chosen module instead of the intended one.

This issue affects oban_web: from 2.12.0 before 2.12.5.

Weakness: CWE-862 (Missing Authorization)

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

3 open source packages ship an affected version, including oban_web.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oban_web` | Hex | From 2.12.0 | 2.12.5 |
| `oban_web` | Hex | From 2.12.0 | 2.12.5 |
| `oban_web` | Hex | From 2.12.0 | 2.12.5 |

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

Upgrade oban_web to 2.12.5 or later.

## Is CVE-2026-48592 being exploited?

There is no known exploitation of CVE-2026-48592 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48592 is a medium-severity missing authorization vulnerability in oban-bg oban_web, published on 26 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48592 in the wild and no public exploit code.

Affected packages and fixed versions:
- oban_web (Hex): affected from 2.12.0; fixed in 2.12.5
- oban_web (Hex): affected from 2.12.0; fixed in 2.12.5
- oban_web (Hex): affected from 2.12.0; fixed in 2.12.5

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-48592/ (Markdown: https://insights.sbomify.com/CVE-2026-48592/index.md)
```

## Sources

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

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