CVE-2026-34148: Resource Exhaustion in @fedify/fedify Due to Unbounded Redirects

@fedify/fedify Updated 07 Apr 2026

Summary

07/04/2026
Yes i
High
7.5

CVE-2026-34148: @fedify/fedify follows HTTP redirects recursively in its remote document loader and authenticated document loader without enforcing a maximum redirect count or visited-URL loop detection. Affects @fedify/fedify across 4 version ranges.

< 1.9.6 >= 1.10.0, < 1.10.5 >= 2.0.0, < 2.0.8 >= 2.1.0, < 2.1.1

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @fedify/fedify package is a library designed for handling ActivityPub requests, enabling decentralized social networking functionalities. It allows servers to verify remote keys and load documents from remote sources. However, it is vulnerable to a resource exhaustion issue caused by unbounded HTTP redirects during the document loading process, which can lead to denial of service.

Vulnerability Detail

The vulnerability arises from the way @fedify/fedify handles HTTP redirects in its document loader. It follows 3xx responses recursively without enforcing a maximum redirect count or detecting loops in visited URLs. An attacker can exploit this by controlling a remote ActivityPub key or actor URL, causing the server to make numerous outbound requests from a single inbound request. This can lead to significant resource consumption, potentially overwhelming the server and resulting in denial of service. The issue has been confirmed in versions 1.9.1 and 1.9.2, and it affects both generic and authenticated document loaders.

How To Fix

Latest published version: 2.4.4 as of 23 Oct 2026

npm install @fedify/fedify@2.4.4

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.9.6 1.9.6
    npm install @fedify/fedify@1.9.6
  • >= 1.10.0, < 1.10.5 1.10.5
    npm install @fedify/fedify@1.10.5
  • >= 2.0.0, < 2.0.8 2.0.8
    npm install @fedify/fedify@2.0.8
  • >= 2.1.0, < 2.1.1 2.1.1
    npm install @fedify/fedify@2.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, you can implement a redirect limit in your application logic when using the document loader. Here is an example of how to set a maximum redirect count:

const MAX_REDIRECTS = 5;
let redirectCount = 0;

async function safeLoader(url) {
  if (redirectCount >= MAX_REDIRECTS) {
    throw new Error('Maximum redirect limit reached');
  }
  redirectCount++;
  return await loader(url);
}

Conclusion

The vulnerability CVE-2026-34148 in the @fedify/fedify package poses a significant risk due to its potential for resource exhaustion through unbounded HTTP redirects. It is crucial to update to the patched versions to mitigate this risk and ensure the stability of your application.

See every vulnerability recorded for @fedify/fedify →

Share this vulnerability

FAQ

CVE-2026-34148 is a vulnerability in the @fedify/fedify package that allows for resource exhaustion due to unbounded HTTP redirects.

An attacker can exploit this vulnerability by controlling a remote ActivityPub key or actor URL, causing the server to follow numerous redirects and consume resources.

The vulnerability has been confirmed in versions 1.9.1 and 1.9.2 of @fedify/fedify.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to test your package-lock.json.

The CVSS score of this vulnerability is 7.5, indicating a high severity level.

Related vulnerabilities

Recent vulnerabilities recorded for @fedify/fedify.

How To Fix

Latest published version: 2.4.4 as of 23 Oct 2026

npm install @fedify/fedify@2.4.4

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.9.6 1.9.6
    npm install @fedify/fedify@1.9.6
  • >= 1.10.0, < 1.10.5 1.10.5
    npm install @fedify/fedify@1.10.5
  • >= 2.0.0, < 2.0.8 2.0.8
    npm install @fedify/fedify@2.0.8
  • >= 2.1.0, < 2.1.1 2.1.1
    npm install @fedify/fedify@2.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback