← Back
CVE-2026-34148
Vulnerability in @fedify/fedify (CVE-2026-34148)
Summary
vulnerability in @fedify/fedify (CVE-2026-34148). Risk of unauthorized operations or information disclosure. Exploitable via ``keyId``. Mitigation: upgrade to `2.1.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-34148** has been found in @fedify/fedify.
Attackers can target a specific entry point like ``keyId`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @fedify/fedify to **2.1.1** or later.
If unsure, ask your IT team or search "@fedify/fedify CVE-2026-34148" on the vendor's site.
CVE-2026-34148 (@fedify/fedify) — CWE-400 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `keyId` / `Location`
Patched: `2.1.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-400) exists in @fedify/fedify. Attackers reach the vulnerable code path via ``keyId`` without authentication.
📍 Affected scope
@fedify/fedify — . Attack surface: `keyId` / `Location`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.1.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@fedify/fedify' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@fedify/fedify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@fedify/fedify` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @fedify/fedify to 2.1.1ステージング環境で 2.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@fedify/fedify
[{"type":"SEMVER","events":[{"introduced":"2.1.0"},{"fixed":"2.1.1"}]}]
npm
@fedify/vocab-runtime
[{"type":"SEMVER","events":[{"introduced":"2.1.0"},{"fixed":"2.1.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-34148
- package https://github.com/fedify-dev/fedify
- web https://github.com/fedify-dev/fedify/security/advisories/GHSA-gm9m-gwc4-hwgp
- web https://github.com/fedify-dev/fedify/releases/tag/1.10.5
- web https://github.com/fedify-dev/fedify/releases/tag/1.9.6
- web https://github.com/fedify-dev/fedify/releases/tag/2.0.8
- web https://github.com/fedify-dev/fedify/releases/tag/2.1.1
- web https://github.com/advisories/GHSA-gm9m-gwc4-hwgp