Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22595: CWE-863: Incorrect Authorization in TryGhost Ghost

0
High
VulnerabilityCVE-2026-22595cvecve-2026-22595cwe-863
Published: Sat Jan 10 2026 (01/10/2026, 02:57:08 UTC)
Source: CVE Database V5
Vendor/Project: TryGhost
Product: Ghost

Description

Ghost is a Node.js content management system. In versions 5.121.0 through 5.130.5 and 6.0.0 through 6.10.3, a vulnerability in Ghost's handling of Staff Token authentication allowed certain endpoints to be accessed that were only intended to be accessible via Staff Session authentication. External systems that have been authenticated via Staff Tokens for Admin/Owner-role users would have had access to these endpoints. This issue has been patched in versions 5.130.6 and 6.11.0.

AI-Powered Analysis

AILast updated: 01/17/2026, 07:52:10 UTC

Technical Analysis

CVE-2026-22595 is an authorization bypass vulnerability classified under CWE-863 affecting the TryGhost Ghost content management system, a popular Node.js-based platform for digital publishing. The vulnerability exists in versions 5.121.0 through 5.130.5 and 6.0.0 through 6.10.3, where the system incorrectly differentiates between Staff Token and Staff Session authentication mechanisms. Staff Tokens, which are intended for external system authentication, were erroneously granted access to certain API endpoints that should have been restricted exclusively to Staff Sessions, which represent authenticated user sessions within the Ghost admin interface. This flaw allows an attacker with a valid Staff Token for an Admin or Owner role to perform unauthorized actions on sensitive endpoints, potentially modifying content, configurations, or disrupting service availability. The vulnerability does not expose confidential data directly but compromises the integrity and availability of the CMS. The CVSS v3.1 score of 8.1 reflects the network exploitable nature, low attack complexity, requirement of privileges (Staff Token), no user interaction, and significant impact on integrity and availability. The issue was publicly disclosed on January 10, 2026, and has been addressed in Ghost versions 5.130.6 and 6.11.0. No public exploits have been observed, but the vulnerability's nature makes it a critical concern for organizations relying on Ghost for content management.

Potential Impact

For European organizations, especially those in media, publishing, and digital content sectors using the Ghost CMS, this vulnerability poses a significant risk. Unauthorized access to administrative endpoints could lead to content tampering, unauthorized configuration changes, or service disruption, impacting business operations and brand reputation. Given the high integrity and availability impact, attackers could deface websites, inject malicious content, or cause denial of service conditions. The vulnerability's exploitation requires possession of a Staff Token with Admin or Owner privileges, which may be obtained through other means such as credential compromise or insider threats. The risk is amplified in environments where external integrations or automated systems use Staff Tokens extensively. Organizations failing to patch promptly may face targeted attacks aiming to disrupt digital presence or manipulate published content, which could have regulatory and compliance implications under European data protection and cybersecurity laws.

Mitigation Recommendations

European organizations should immediately upgrade affected Ghost CMS instances to versions 5.130.6 or 6.11.0 or later to remediate the vulnerability. Additionally, review and restrict the issuance and scope of Staff Tokens, ensuring they are granted only to trusted external systems with minimal necessary privileges. Implement strict monitoring and logging of API access, focusing on Staff Token usage patterns to detect anomalous activities. Employ network segmentation to isolate CMS management interfaces and limit exposure to external networks. Conduct regular audits of user roles and token permissions to minimize privilege creep. Where possible, enforce multi-factor authentication for administrative access and rotate tokens periodically. Finally, integrate vulnerability management processes to promptly identify and patch similar authorization issues in third-party software components.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-07T21:50:39.532Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6961c40f19784dcf52ace878

Added to database: 1/10/2026, 3:14:23 AM

Last enriched: 1/17/2026, 7:52:10 AM

Last updated: 2/6/2026, 7:56:11 PM

Views: 89

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats