CVE-2026-71246: Pixelfed: Authenticated SSRF via Remote URL Search

Published Aug 5, 2026
·
Updated

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.

Affected Software

1 affected component
Pixelfed

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Harden URL validation in ActivityPubFetchService::validateUrl() so it does not only block literal hosts (127.0.0.1, localhost, ::1) and requires https, but also blocks URLs whose resolved IP falls within private/internal/link-local ranges (e.g., 169.254.169.254).

    Pixelfed SearchController / ActivityPubFetchService validateUrl() remote-search URL validation = Require resolved IP to be outside private, internal, and link-local ranges
  2. Compensating control

    Block outbound requests from Pixelfed to link-local and private/internal address ranges to mitigate SSRF to 169.254.169.254 (and other internal ranges).

Event History

Aug 5, 2026
CVE Published
via MITRE·10:56 AM
Data Sourced
via MITRE·10:56 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-71246?

The severity of CVE-2026-71246 is rated as medium with a score of 5.7.

2

How do I fix CVE-2026-71246?

To fix CVE-2026-71246, ensure that the URL validation in the SearchController is enhanced to block potentially dangerous hosts and perform rigorous IP checking.

3

What is the main risk associated with CVE-2026-71246?

The main risk associated with CVE-2026-71246 is the potential for authenticated SSRF attacks via the remote-search parameters.

4

Which service is affected by CVE-2026-71246?

CVE-2026-71246 affects the Pixelfed application, specifically the SearchController and its interaction with the ActivityPubFetchService.

5

When was CVE-2026-71246 published?

CVE-2026-71246 was published on August 5, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203