CVE-2026-53946
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGhost is a Node.js content management system. From 6.19.4 until 6.21.1, when re-rendering posts, Ghost would refetch missing image dimensions by issuing an outbound HTTP request to the URL stored on an image card — without restricting that URL to trusted image hosts. An authenticated staff user able to create or edit posts could therefore point an image card at an attacker-chosen host and cause the Ghost server to request it on their behalf, including hosts on internal networks or cloud instance metadata endpoints that would not normally be reachable from the public internet. This vulnerability is fixed in 6.21.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGhost CMS versions 6.19.4 through 6.21.1 contain an authenticated Server-Side Request Forgery (SSRF) vulnerability. When re-rendering posts with image cards that have missing dimensions, Ghost issues outbound HTTP requests to fetch those dimensions without validating that the URL points to a trusted image host. An authenticated staff user with post create/edit permissions can exploit this by setting an image URL to internal network hosts or cloud metadata endpoints (e.g., 169.254.169.254), allowing enumeration of internal infrastructure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Ghost CMS versionAccess the Ghost admin panel and navigate to Settings > About, or check the installed package.json file in the Ghost installation directory to identify the exact version number.Affected if The installed version falls within the range 6.19.4 through 6.21.1 (inclusive). Versions below 6.19.4 or above 6.21.1 are not affected by this specific vulnerability.
-
Verify authenticated user permissionsIn the Ghost admin panel, navigate to Settings > Staff and review user roles. Staff users with 'Editor' or 'Author' roles have post create/edit permissions that could exploit this vulnerability.Affected if Any active staff user account with post create or edit permissions exists in the system.
-
Identify posts with image cardsReview published or draft posts in the Ghost content management system. Examine posts that contain image cards, particularly those where image dimension metadata may be missing or incomplete.Affected if The system contains posts with image cards that could trigger the dimension-fetching HTTP requests when re-rendered.
-
Monitor for suspicious outbound requestsReview Ghost server logs and network traffic for outbound HTTP requests originating from the Ghost application. Specifically look for requests to IP addresses in private ranges (10.x.x.x, 172.16-31.x.x, 192.168.x.x) or cloud metadata endpoints (169.254.169.254).Affected if Outbound HTTP requests from the Ghost server are observed targeting internal network addresses or cloud metadata services.
Your environment is affected if Ghost CMS version is between 6.19.4 and 6.21.1 inclusive and you have authenticated staff users with post editing capabilities, allowing them to insert image cards that trigger uncontrolled outbound HTTP requests to internal or metadata endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Ghost to version 6.21.1 or later. If immediate upgrade is not feasible, consider restricting outbound network access from the Ghost server and monitoring for suspicious requests to internal IP ranges or metadata endpoints.
6.21.1 or later
- Backup your Ghost database and content files before upgrading
- Verify current Ghost version using `ghost version` or checking the admin panel
- Upgrade Ghost to version 6.21.1 or later using the Ghost CLI: `ghost update v6.21.1` or simply `ghost update` to get the latest stable version
- After upgrade, verify the new version is running: `ghost version`
- Test that authenticated staff users can no longer trigger arbitrary outbound requests via image card URLs
- Review Ghost release notes for 6.21.1 to confirm the SSRF fix is included
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53946 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53946 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data