Skip to main content
Menu
CVEs

Manyfold server-side request forgery in ActivityPub avatar fetching

CVE-2026-133237EUVD-2026-130319Published November 19, 2026, updated

6.9MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 0.154.2
Who is exposed
Not reported

Summary

Manyfold has a server-side request forgery flaw that lets an attacker, remotely and without logging in, make the server fetch internal URLs, including cloud metadata hosts. The attacker does this by sending Create or Update activities with malicious ActivityPub actor icon and image URLs to the inbox, and the server stores the responses as creator avatar or banner attachments.

Written by a model

Original 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.

What to do

Upgrade to a fixed version: 0.154.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133237 (Manyfold 0.124.0 before 0.154.2 SSRF via ActivityPub Actor Icon and Image URLs), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133237 (entry last updated 2026-11-19):
Affected:
- manyfold3d manyfold: from 0.124.0, fixed in 0.154.2
Fixed versions: 0.154.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133237 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133237 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/manyfold3d/manyfold/security/advisories/GHSA-j84g-7c58-cx6j
- https://github.com/manyfold3d/manyfold/pull/7590
- https://github.com/manyfold3d/manyfold/commit/cef818b47dbf71b6b4b4d3e096b420f231a5bc29
- https://github.com/manyfold3d/manyfold/releases/tag/v0.154.2
- https://github.com/manyfold3d/manyfold/blob/v0.153.0/app/deserializers/activity_pub/creator_deserializer.rb#L22-L23
- https://github.com/manyfold3d/manyfold/blob/v0.153.0/app/uploaders/application_uploader.rb#L22
- https://github.com/manyfold3d/manyfold
- https://www.vulncheck.com/advisories/manyfold-0.124.0-before-0.154.2-ssrf-via-activitypub-actor-icon-and-image-urls
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133237
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133237"}.

Affected versions

cve.now Index

42Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 10

Questions about CVE-2026-133237

Is CVE-2026-133237 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133237?

manyfold: from 0.124.0 before 0.154.2.

Source: cve.now feed data

How do I fix CVE-2026-133237?

Upgrade to a fixed version: 0.154.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.