CVE-2026-71246

Pixelfed - Authenticated SSRF via Remote URL Search

Published Aug 5, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
Pixelfed's SearchController (behind the auth middleware) accepts a URL via its remote-search parameters and fetches it server-side through ActivityPubFetchService, whose validateUrl only blocks the literal hosts 127.0.0.1, localhost, and ::1 and requires https, without checking the resolved IP against private, internal, or link-local ranges (e.g. 169.254.169.254).

Analysis

AI-generated

Technical impact

Pixelfed's SearchController, which requires authentication, receives a URL parameter for remote search and fetches that URL via ActivityPubFetchService. The validator for the URL only blocks the literal hosts 127.0.0.1, localhost, and ::1 and enforces an HTTPS scheme, but it does not check whether the resolved IP address lies within private, internal, or link‑local ranges such as 169.254.169.254. Consequently, an authenticated user can cause the server to issue outbound requests to arbitrary hosts, including internal services or instance metadata endpoints. This flaw is a form of authenticated server‑side request forgery (CWE‑918).

Affected Systems

Any Pixelfed deployment built with the pixelfed:pixelfed package that includes the SearchController and ActivityPubFetchService without a patched URL validator is affected. No specific version range is documented in the advisory, so all current releases should be examined for the same code paths.

Risk and Exploitability

The CVSS score is 4.3, indicating moderate severity. The EPSS score is less than 1 %, reflecting a low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Attackers must be authenticated to exploit the flaw, which limits the surface to active users. Once authenticated, the attacker can direct the server to access internal or remote systems, potentially discovering internal resources or extracting sensitive data discovered over HTTP/HTTPS. Overall, the risk is moderate but warrants timely remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a version of Pixelfed that implements the secure URL validation logic in ActivityPubFetchService.
  • If an upgrade is not immediately possible, disable the remote‑search feature in the SearchController or configure it to reject external URLs entirely.
  • Adjust the URL validation to reject any URL whose resolved IP falls within private, internal, or link‑local address ranges, ensuring the server can only reach public addresses.

Generated by OpenCVE AI on August 10, 2026 at 22:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
Description Pixelfed's SearchController (behind the auth middleware) accepts a URL via its remote-search parameters and fetches it server-side through ActivityPubFetchService, whose validateUrl() only blocks the literal hosts 127.0.0.1, localhost, and ::1 and requires https, without checking the resolved IP against private, internal, or link-local ranges (e.g. 169.254.169.254). Optional DNS validation is disabled by default and, when enabled, only confirms a DNS record exists without filtering by IP range. The fetch response body is returned to the requester only when the Content-Type matches an ActivityPub content type, making this a semi-blind but authenticated SSRF primitive reachable by any logged-in user. Pixelfed's SearchController (behind the auth middleware) accepts a URL via its remote-search parameters and fetches it server-side through ActivityPubFetchService, whose validateUrl only blocks the literal hosts 127.0.0.1, localhost, and ::1 and requires https, without checking the resolved IP against private, internal, or link-local ranges (e.g. 169.254.169.254).
Type Values Removed Values Added
Title Pixelfed: Authenticated SSRF via Remote URL Search Pixelfed - Authenticated SSRF via Remote URL Search
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Type Values Removed Values Added
First Time appeared Pixelfed
Pixelfed pixelfed
Vendors & Products Pixelfed
Pixelfed pixelfed
Type Values Removed Values Added
Description Pixelfed's SearchController (behind the auth middleware) accepts a URL via its remote-search parameters and fetches it server-side through ActivityPubFetchService, whose validateUrl() only blocks the literal hosts 127.0.0.1, localhost, and ::1 and requires https, without checking the resolved IP against private, internal, or link-local ranges (e.g. 169.254.169.254). Optional DNS validation is disabled by default and, when enabled, only confirms a DNS record exists without filtering by IP range. The fetch response body is returned to the requester only when the Content-Type matches an ActivityPub content type, making this a semi-blind but authenticated SSRF primitive reachable by any logged-in user.
Title Pixelfed: Authenticated SSRF via Remote URL Search
Weaknesses CWE-918
References
Metrics cvssV3_1

{'score': 5.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
TuranSec
Published
Updated
Aug 10, 2026, 11:45 AM
Reserved
Aug 5, 2026, 10:53 AM
Status
Deferred
Published
Aug 5, 2026, 11:16 AM
Modified
Aug 26, 2026, 5:13 PM