# CVE-2026-133237: Manyfold 0.124.0 before 0.154.2 SSRF via ActivityPub Actor Icon and Image URLs


- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-j84g-7c58-cx6j, GHSA-mfff-g47g-wmwh

## What is CVE-2026-133237?

CVE-2026-133237 is a medium-severity vulnerability in manyfold3d manyfold, published on 19 Nov 2026. 

### Official description

Manyfold 0.124.0 before 0.154.2 contains a server-side request forgery vulnerability that allows unauthenticated remote attackers to make the instance fetch internal URLs by supplying malicious ActivityPub actor icon.url and image.url fields. Attackers can deliver Create or Update activities to the inbox, causing the Shrine remote_url plugin to request internal or cloud metadata hosts and store responses as creator avatar or banner attachments.

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

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

1 open source package ship an affected version, including manyfold3d/manyfold.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `manyfold3d/manyfold` | GitHub | `pkg:github/manyfold3d/manyfold` | From 0.124.0 | 0.154.2 |

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

Upgrade manyfold3d/manyfold to 0.154.2 or later.

## Is CVE-2026-133237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133237 is a medium-severity vulnerability in manyfold3d manyfold, published on 19 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-133237 exists.

Affected packages and fixed versions:
- manyfold3d/manyfold (GitHub): affected from 0.124.0; fixed in 0.154.2

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

## Sources

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

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