Skip to main content
CVE-2025-68475VulnerabilityPublished

CVE-2025-68475: fedify · ReDoS

Affects fedifySource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 1.6.13 soon.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.6.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade fedify to 1.6.13.

Affected software

ProductAffectedFixed in
fedify-dev fedifyAffected
  • <1.6.13
Fixed in
  • 1.6.13

AI-suggested

European organizations should immediately audit their use of the Fedify library within federated server applications and identify any deployments running vulnerable versions. The primary mitigation is to upgrade Fedify to the patched versions 1.6.13, 1.7.14, 1.8.15, or 1.9.2 or later, depending on the version branch in use. Where immediate upgrading is not feasible, organizations should implement network-level protections such as rate limiting and input validation to detect and block suspiciously large or malformed HTML responses that could trigger the ReDoS condition. Monitoring CPU usage and application logs for signs of excessive backtracking or performance degradation can provide early warning of exploitation attempts. Developers should review and refactor any custom regular expressions in their ActivityPub implementations to avoid nested quantifiers or other inefficient patterns. Employing Web Application Firewalls (WAFs) with rules targeting ReDoS attack signatures may provide additional defense. Finally, organizations should maintain an incident response plan to quickly address denial of service incidents affecting federated services.

Description

Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Prior to versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2, a Regular Expression Denial of Service (ReDoS) vulnerability exists in Fedify's document loader. The HTML parsing regex at packages/fedify/src/runtime/docloader.ts:259 contains nested quantifiers that cause catastrophic backtracking when processing maliciously crafted HTML responses. This issue has been patched in versions 1.6.13, 1.7.14, 1.8.15, and 1.9.2.

References

Community reviews

Loading reviews…