Vulnerability Database · npm · @fedify/fedify · Version
@fedify/fedify 2.0.32-dev.2368
2.0.32-dev.2368 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 08 Oct 2026
Licence MIT
Also known from other sources 0
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version
@fedify/fedify 2.0.32-dev.2368 vulnerabilities
1 vulnerability cover @fedify/fedify 2.0.32-dev.2368. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-42462: Fedify LD-Signature Bypass via JSON-LD Named-Graph Restructuring | 7.0 high | 2.2.3 | 26 May 2026 |
Looking for another version, or everything Vulert holds for @fedify/fedify?
Questions
About @fedify/fedify 2.0.32-dev.2368
Is @fedify/fedify 2.0.32-dev.2368 vulnerable?
Yes. 1 vulnerability in the Vulert database cover @fedify/fedify 2.0.32-dev.2368: 0 critical, 1 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 2.0.32-dev.2368 the latest release of @fedify/fedify?
No. 2.0.32-dev.2368 was published 08 Oct 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.