Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-7120 medium CVSS 5.3

Vulnerability in @fastify/static (CVE-2026-7120)

Summary

Vulnerability in @fastify/static (CVE-2026-7120). Risk of unauthorized operations or information disclosure. Exploitable via allowedPath. Mitigation: upgrade to 10.1.2 or later.

Original description

The description as published by the source.

Impact

@fastify/static evaluates the allowedPath callback before normalizing dot segments and duplicate slashes in the pathname used for file resolution. Non-canonical pathnames such as //file, /./file, or /public/../private/file bypass allowedPath filtering while resolving to the intended file on disk.

Applications that use allowedPath as a security boundary to restrict access to specific static files or path subtrees may unintentionally expose files that were intended to be denied.

Patches

Upgrade to @fastify/static >= 10.1.2.

Workarounds

None. Upgrade to the patched version.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-7120 has been found in @fastify/static.
Attackers can target a specific entry point like allowedPath over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade @fastify/static to 10.1.2 or later.
If unsure, ask your IT team or search "@fastify/static CVE-2026-7120" on the vendor's site.

CVE-2026-7120 (@fastify/static) — CWE-180 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: allowedPath
Patched: 10.1.2 — apply immediately
Workaround: None.
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-180) exists in @fastify/static. Attackers reach the vulnerable code path via allowedPath without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @fastify/static. Attack surface: allowedPath.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 10.1.2.

🛡️ Workaround

Workaround: None.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@fastify/static' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@fastify/static' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @fastify/static を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    None.

    パッチが適用されるまでの応急処置として、None. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade @fastify/static to 10.1.2

    ステージング環境で 10.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @fastify/static
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"10.1.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details