VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@fedify/fedify: vulnerability history, versions and safety

@fedify/fedify is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 43 releases, from Jul 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H5 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 14 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @fedify/fedify vulnerabilities

Vulert verdict on @fedify/fedify 2.4.4 i

Updated on 23 Oct 2026

Good news: 2.4.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 2.4.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.4.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.4.4 — unaffected i
  • Vulnerabilities on record 7 over 2 years · 4 in the last year i
  • Latest disclosure 14 Jul 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Depended on by 15 packages i
  • Stars 1,031 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @fedify/fedify, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.0.35-dev.2480 22 Oct 2026 H1 MIT Yes Details →
2.0.35-dev.2470 21 Oct 2026 H1 MIT Yes Details →
2.0.35-dev.2469 20 Oct 2026 H1 MIT Yes Details →
2.0.35-dev.2468 20 Oct 2026 H1 MIT Yes Details →
2.0.35-dev.2465 20 Oct 2026 H1 MIT Yes Details →
2.4.5-dev.2462 19 Oct 2026 none MIT — Details →
2.0.35-dev.2459 19 Oct 2026 H1 MIT Yes Details →
2.4.5-dev.2453 19 Oct 2026 none MIT — Details →
2.4.5-dev.2451 18 Oct 2026 none MIT — Details →
2.5.0-dev.2448 17 Oct 2026 none MIT — Details →
2.5.0-dev.2446 16 Oct 2026 none MIT — Details →
2.4.5-dev.2442 14 Oct 2026 none MIT — Details →
2.5.0-dev.2440 13 Oct 2026 none MIT — Details →
2.5.0-dev.2432 12 Oct 2026 none MIT — Details →
2.4.4 12 Oct 2026 none MIT — Details →
2.3.14 12 Oct 2026 none MIT — Details →
2.2.19 12 Oct 2026 none MIT — Details →
2.1.30 12 Oct 2026 H1 MIT Yes Details →
2.0.34 12 Oct 2026 H1 MIT Yes Details →
2.5.0-dev.2424 12 Oct 2026 none MIT — Details →
2.0.34-dev.2423 12 Oct 2026 H1 MIT Yes Details →
2.0.34-dev.2422 12 Oct 2026 H1 MIT Yes Details →
2.5.0-dev.2420 11 Oct 2026 none MIT — Details →
2.4.3 11 Oct 2026 none MIT — Details →
2.3.13 11 Oct 2026 none MIT — Details →
2.2.18 11 Oct 2026 none MIT — Details →
2.1.29 11 Oct 2026 H1 MIT Yes Details →
2.0.33 11 Oct 2026 H1 MIT Yes Details →
2.0.33-dev.2414 11 Oct 2026 H1 MIT Yes Details →
2.0.33-dev.2413 11 Oct 2026 H1 MIT Yes Details →
2.0.33-dev.2393 09 Oct 2026 H1 MIT Yes Details →
2.2.18-dev.2386 09 Oct 2026 none MIT — Details →
2.0.33-dev.2381 09 Oct 2026 H1 MIT Yes Details →
2.0.33-dev.2380 09 Oct 2026 H1 MIT Yes Details →
2.5.0-dev.2378 08 Oct 2026 none MIT — Details →
2.4.2 08 Oct 2026 none MIT — Details →
2.3.12 08 Oct 2026 none MIT — Details →
2.2.17 08 Oct 2026 none MIT — Details →
2.1.28 08 Oct 2026 H1 MIT Yes Details →
2.0.32 08 Oct 2026 H1 MIT Yes Details →
2.0.32-dev.2371 08 Oct 2026 H1 MIT Yes Details →
2.5.0-dev.2370 08 Oct 2026 none MIT — Details →
2.0.32-dev.2368 08 Oct 2026 H1 MIT Yes Details →
2.5.0-dev.2364 08 Oct 2026 none MIT — Details →
2.3.12-dev.2365 08 Oct 2026 none MIT — Details →
2.4.2-dev.2362 08 Oct 2026 none MIT — Details →
2.5.0-dev.2358 06 Oct 2026 none MIT — Details →
2.4.2-dev.2357 06 Oct 2026 none MIT — Details →
2.5.0-dev.2355 06 Oct 2026 none MIT — Details →
2.0.32-dev.2352 06 Oct 2026 H1 MIT Yes Details →
2.0.32-dev.2351 06 Oct 2026 H1 MIT Yes Details →
2.4.2-dev.2347 06 Oct 2026 none MIT — Details →
2.3.12-dev.2346 06 Oct 2026 none MIT — Details →
2.0.32-dev.2345 06 Oct 2026 H1 MIT Yes Details →
2.3.12-dev.2341 06 Oct 2026 none MIT — Details →
2.5.0-dev.2339 06 Oct 2026 none MIT — Details →
2.5.0-dev.2332 05 Oct 2026 none MIT — Details →
2.5.0-dev.2327 05 Oct 2026 none MIT — Details →
2.4.1 05 Oct 2026 none MIT — Details →
2.3.11 05 Oct 2026 none MIT — Details →
2.2.16 05 Oct 2026 none MIT — Details →
2.1.27 05 Oct 2026 H1 MIT Yes Details →
2.0.31 05 Oct 2026 H1 MIT Yes Details →
2.0.31-dev.2316 05 Oct 2026 H1 MIT Yes Details →
2.5.0-dev.2314 05 Oct 2026 none MIT — Details →
2.0.31-dev.2310 04 Oct 2026 H1 MIT Yes Details →
2.0.31-dev.2308 04 Oct 2026 H1 MIT Yes Details →
2.5.0-dev.2304 04 Oct 2026 none MIT — Details →
2.0.31-dev.2306 04 Oct 2026 H1 MIT Yes Details →
2.0.31-dev.2297 04 Oct 2026 H1 MIT Yes Details →
2.3.11-dev.2296 04 Oct 2026 none MIT — Details →
2.5.0-dev.2289 04 Oct 2026 none MIT — Details →
2.5.0-dev.2287 04 Oct 2026 none MIT — Details →
2.5.0-dev.2281 04 Oct 2026 none MIT — Details →
2.3.11-dev.2280 03 Oct 2026 none MIT — Details →
2.0.31-dev.2273 03 Oct 2026 H1 MIT Yes Details →
2.5.0-dev.2271 02 Oct 2026 none MIT — Details →
2.4.0 30 Sep 2026 none MIT — Details →
2.4.0-dev.2260 30 Sep 2026 none MIT — Details →
2.4.0-dev.2259 30 Sep 2026 none MIT — Details →
2.4.0-dev.2256 30 Sep 2026 none MIT — Details →
2.4.0-dev.2253 30 Sep 2026 none MIT — Details →
2.4.0-dev.2247 30 Sep 2026 none MIT — Details →
2.4.0-dev.2245 30 Sep 2026 none MIT — Details →
2.4.0-dev.2240 30 Sep 2026 none MIT — Details →
2.4.0-dev.2233 30 Sep 2026 none MIT — Details →
2.4.0-dev.2228 30 Sep 2026 none MIT — Details →
2.4.0-dev.2219 30 Sep 2026 none MIT — Details →
2.3.10 30 Sep 2026 none MIT — Details →
2.4.0-dev.2212 30 Sep 2026 none MIT — Details →
2.2.15 30 Sep 2026 none MIT — Details →
2.1.26 30 Sep 2026 H1 MIT Yes Details →
2.0.30 30 Sep 2026 H1 MIT Yes Details →
2.0.30-dev.2202 30 Sep 2026 H1 MIT Yes Details →
2.4.0-dev.2200 30 Sep 2026 none MIT — Details →
2.0.30-dev.2199 30 Sep 2026 H1 MIT Yes Details →
2.2.15-dev.2196 30 Sep 2026 none MIT — Details →
2.4.0-dev.2193 30 Sep 2026 none MIT — Details →
2.4.0-dev.2190 30 Sep 2026 none MIT — Details →
2.0.30-dev.2188 30 Sep 2026 H1 MIT Yes Details →
2.4.0-dev.2169 30 Sep 2026 none — — Details →
2.4.0-dev.2164 30 Sep 2026 none — — Details →
2.4.0-dev.2159 29 Sep 2026 none — — Details →
2.4.0-dev.2157 29 Sep 2026 none — — Details →
2.3.9 29 Sep 2026 none — — Details →
2.4.0-dev.2155 29 Sep 2026 none — — Details →
2.2.14 29 Sep 2026 none — — Details →
2.1.25 29 Sep 2026 H1 — Yes Details →
2.4.0-dev.2149 29 Sep 2026 none — — Details →
2.0.29 29 Sep 2026 H1 — Yes Details →
2.4.0-dev.2141 29 Sep 2026 none — — Details →
2.0.29-dev.2143 29 Sep 2026 H1 — Yes Details →
2.0.29-dev.2139 29 Sep 2026 H1 — Yes Details →
2.4.0-dev.2129 29 Sep 2026 none — — Details →
2.4.0-dev.2127 29 Sep 2026 none — — Details →
2.4.0-dev.2122 29 Sep 2026 none — — Details →
2.0.29-dev.2121 29 Sep 2026 H1 — Yes Details →
2.4.0-dev.2115 29 Sep 2026 none — — Details →
2.4.0-dev.2108 29 Sep 2026 none — — Details →
2.0.29-dev.2107 29 Sep 2026 H1 — Yes Details →

The newest 120 of 1,611 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 3
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @fedify/fedify

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-54888: @fedify/fedify Authentication Bypass and Actor Impersonation Vulnerability 8.7 high 1.3.20 08 Aug 2025
CVE-2026-50131: Fedify Incomplete SSRF Mitigation Allows Special-Use IPv4 Access 8.6 high 1.9.12 14 Jul 2026
ReDoS Vulnerability in Fedify Package: HTML Parsing Regex Issue 7.5 high 1.6.13 22 Dec 2025
CVE-2026-34148: Resource Exhaustion in @fedify/fedify Due to Unbounded Redirects 7.5 high 1.9.6 07 Apr 2026
CVE-2024-39687: Server Side Request Forgery (SSRF) attack in Fedify 7.2 medium 0.9.2 05 Jul 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 →

Questions

About @fedify/fedify

Is @fedify/fedify safe to use?

Vulert records 7 vulnerabilities for @fedify/fedify in npm: 0 critical, 5 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @fedify/fedify's Vulert package health score?

Vulert scores @fedify/fedify 75/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @fedify/fedify affected?

No. 2.4.4, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @fedify/fedify have?

7 vulnerabilities are recorded for @fedify/fedify in the npm ecosystem: 0 critical, 5 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @fedify/fedify vulnerabilities disclosed?

4 vulnerabilities were recorded for @fedify/fedify in the last 12 months, and the oldest entry in this database dates to 05 Jul 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @fedify/fedify are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @fedify/fedify for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @fedify/fedify version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.