# CVE-2026-47161: RELATE Vulnerable to Remote Code Execution (RCE) via Insecure Celery Pickle Deserialization

> An attacker with broker access or an authenticated student can achieve remote code execution on the host server via insecure Celery pickle deserialization.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** No
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-4mwh-mwv4-m252

## What is CVE-2026-47161?

CVE-2026-47161 is a high-severity unsafe deserialization vulnerability in inducer relate, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RELATE is a web-based courseware package. Prior to commit d66ba5659b459bf1ba56b7109b5f9ecf197cbefb, RELATE LMS configures its Celery workers to accept and deserialize untrusted 'pickle' data. An attacker who can reach the message broker can execute arbitrary commands on the host server. Combined with missing network isolation in the code execution sandbox, this allows an authenticated student to achieve full Remote Code Execution (RCE) on the host system. Commit d66ba5659b459bf1ba56b7109b5f9ecf197cbefb fixes the issue.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-47161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47161 is a high-severity unsafe deserialization vulnerability in inducer relate, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47161 exists.

Affected product: inducer relate. 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-47161/ (Markdown: https://insights.sbomify.com/CVE-2026-47161/index.md)
```

## Sources

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

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