Categories
CVE-2026-53943 critical CVSS 9.6

Vulnerability in ghost (CVE-2026-53943)

Summary

Vulnerability in ghost (CVE-2026-53943). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.37.0 or later.

Original description

The description as published by the source.

Ghost is a Node.js content management system. From until 6.37.0, when Ghost is behind a shared caching layer that results in cached content being shared between different visitors, an unauthenticated user could send an x-ghost-preview header that altered the rendered frontend response. In affected cache configurations, that response could be stored and served to subsequent visitors requesting the same page, allowing cache poisoning of request-specific preview output. When running Ghost's frontend and admin panel on the same domain this could be used to take over staff user accounts. When running these on different domains staff accounts have no exposure. This vulnerability is fixed in 6.37.0.

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-53943 has been found in ghost.
Successful exploitation can lead to full system takeover. CVSS score: 9.6/10.
What to do: upgrade ghost to 6.37.0 or later.
If unsure, ask your IT team or search "ghost CVE-2026-53943" on the vendor's site.

CVE-2026-53943 (ghost) — CWE-524 / CVSS v3 9.6
Attack vector: remote (network-reachable) / unauthenticated
Patched: 6.37.0 — apply immediately
Workaround: At the caching layer, bypass the cache for x-ghost-preview requests.
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-524) exists in ghost.

📍 Affected scope

Check the vendor advisory for the affected versions of ghost.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 6.37.0.

🛡️ Workaround

Workaround: At the caching layer, bypass the cache for x-ghost-preview requests.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ghost' . 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 'ghost' . | grep -v node_modules

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

  2. 2
    Apply temporary workaround mitigate
    At the caching layer, bypass the cache for `x-ghost-preview` requests.

    パッチが適用されるまでの応急処置として、At the caching layer, bypass the cache for x-ghost-preview requests. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade ghost to 6.37.0

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

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

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

Affected packages

npm ghost
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"6.37.0"}]}]
Bitnami ghost
[{"type":"SEMVER","events":[{"introduced":"4.0.0"},{"fixed":"6.37.0"}]}]

References

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