cve.bz

CVE-2026-42462 fedify-dev fedify: Interpretation Conflict

7.0 highEPSS 0.2%Fix available

High (7.0) in fedify-dev fedify. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @fedify/fedify 1.10.10, 1.9.11, 2.0.18.

On this page
Fedify is a TypeScript library for building federated server apps powered by ActivityPub. Prior to versions 1.9.11, 1.10.10, 2.0.18, 2.1.14, and 2.2.3, an attacker can make use of JSON-LD features to restructure a JSON-LD document that would change how Fedify interprets it without changing its Linked Data Signature, allowing them to alter a third-party signed activity they have received. Versions 1.9.11, 1.10.10, 2.0.18, 2.1.14, and 2.2.3 fix the issue.

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-180 Incorrect Behavior Order: Validate Before Canonicalize
CWE-347 Improper Verification of Cryptographic Signature
CWE-436 Interpretation Conflict
CWE-1289 Improper Validation of Unsafe Equivalence in Input
OWASP Top 10
A04:2025 Cryptographic Failures, A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @fedify/fedify (npm): fixed in 2.2.3, 2.1.14, 2.0.18, 1.10.10, 1.9.11

Ask an AI about this CVE

Show the promptExplain CVE-2026-42462 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-42462?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-42462?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-42462 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
fedify-dev fedify>= 2.2.0, < 2.2.3
fedify-dev fedify>= 2.1.0, < 2.1.14
fedify-dev fedify>= 2.0.0, < 2.0.18
fedify-dev fedify>= 1.10.0, < 1.10.10
fedify-dev fedify< 1.9.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9rfg-v8g9-9367npm@fedify/fedify>=2.2.0 <2.2.32.2.3
GHSA-9rfg-v8g9-9367npm@fedify/fedify>=2.1.0 <2.1.142.1.14
GHSA-9rfg-v8g9-9367npm@fedify/fedify>=2.0.0 <2.0.182.0.18
GHSA-9rfg-v8g9-9367npm@fedify/fedify>=1.10.0 <1.10.101.10.10
GHSA-9rfg-v8g9-9367npm@fedify/fedify<1.9.111.9.11

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High
  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-180.

References

Check your stackJSON