CVE-2026-55420 Discourse PDF Upload RCE Vulnerability: Patch & Detection Guide
Discourse, a popular open-source discussion platform, contains a vulnerability in how it processes PDF file uploads under certain non-default server configurations. An authenticated user could exploit this flaw to execute arbitrary code on the server hosting Discourse. The vulnerability affects multiple version branches and has been patched in recent releases across the supported version lines.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-78
- Affected products
- 2 configuration(s)
- Published / Modified
- 2026-07-09 / 2026-07-14
NVD description (verbatim)
Discourse is an open-source discussion platform. Prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5, under certain non-default configurations, processing of PDF uploads could be exploited to obtain RCE on the server. This issue is patched in 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5.
6 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-55420 is a command injection vulnerability (CWE-78) in Discourse's PDF upload handling mechanism. The issue manifests only when specific non-default configurations are enabled, suggesting the vulnerability lies in optional PDF processing features or integrations. An attacker with user-level authentication can supply a malicious PDF that, when processed by the server, results in arbitrary command execution with the privileges of the Discourse application process. The CVSS 3.1 score of 7.5 (HIGH) reflects high confidentiality and integrity impact, though the attack requires valid user credentials and specific server configuration (AC:H).
Business impact
A successful exploit allows authenticated attackers to gain remote code execution on Discourse infrastructure, enabling data theft, platform compromise, malware deployment, and service disruption. Organizations relying on Discourse for community management, customer support, or internal collaboration face operational risk and potential regulatory implications if user data is exfiltrated. The requirement for valid user authentication somewhat limits blast radius, but insider threats or compromised user accounts can weaponize this vulnerability.
Affected systems
Discourse installations running versions prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 are vulnerable. Organizations must identify which version branch they operate and verify they are running the patched release or later within that branch. The vulnerability only manifests with certain non-default configurations, so administrators should review PDF processing settings to understand their exposure.
Exploitability
Exploitation requires valid user credentials (PR:L in CVSS vector), placing this outside the scope of anonymous or unauthenticated attacks. However, the attack complexity is marked as high (AC:H), likely due to the non-default configuration requirement. Once those conditions are met, no user interaction is needed to trigger the flaw—a simple PDF upload initiates the vulnerable processing pipeline. This makes it a reliable vector for authenticated insiders or accounts compromised through phishing or credential stuffing.
Remediation
Upgrade Discourse to a patched version immediately: 2026.6.0 or later for the main branch, 2026.5.1 or later for the 2026.5.x line, 2026.4.2 or later for the 2026.4.x line, or 2026.1.5 or later for the 2026.1.x line. If immediate patching is not feasible, disable or restrict PDF upload functionality and review non-default PDF processing configurations to understand which features expose the vulnerability. Restrict upload permissions to trusted user roles as an interim control.
Patch guidance
Consult the official Discourse release notes and security advisories for version 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 to confirm patch contents and any compatibility notes. Test patches in a staging environment, paying particular attention to PDF-related functionality and any custom PDF processing integrations. Plan upgrades according to your deployment model (managed Discourse Cloud, self-hosted container, or traditional installation) and schedule downtime if necessary. Verify patch application by checking Discourse version in the admin dashboard post-upgrade.
Detection guidance
Monitor server logs for unusual PDF upload patterns, particularly from user accounts with elevated privileges or atypical upload frequency. Watch for error messages related to PDF processing or external command execution. Implement file integrity monitoring on the Discourse application directory to detect unauthorized code changes. Deploy web application firewalls or intrusion detection systems tuned to recognize attempts to inject shell metacharacters into multipart form uploads. Track user account authentication logs for anomalies that might indicate compromised credentials being used to upload PDFs.
Why prioritize this
While the CVSS score is 7.5 (HIGH) and the vulnerability does allow RCE, the requirement for valid user authentication and non-default configuration limits immediate organizational risk compared to unauthenticated remote exploits. However, RCE severity and the realistic threat of insider attacks or credential compromise warrant prompt patching. Organizations with public-facing Discourse instances, particularly those with large user bases, should prioritize this higher due to increased likelihood of account compromise.
Risk score, explained
The 7.5 CVSS score reflects the severity of remote code execution (high impact to confidentiality, integrity, and availability) tempered by attack vector and complexity constraints. The network attack vector (AV:N) provides full accessibility, but high attack complexity (AC:H) accounts for the non-default configuration requirement. The low privilege requirement (PR:L) means an authenticated user suffices—a realistic threat when considering user proliferation, credential leaks, and insider risk. No user interaction (UI:N) is needed once the attacker gains access, making exploitation reliable.
Frequently asked questions
Our Discourse instance uses default configuration. Are we affected?
The vulnerability explicitly requires non-default configurations to be exploited. Review your Discourse admin settings under file uploads and PDF processing features. If you have not explicitly enabled special PDF handling, third-party PDF converters, or related integrations, you are likely not exposed. However, upgrade anyway as a precaution and to eliminate any ambiguity about your configuration.
Do we need to rotate user credentials after patching?
If you have no evidence of unauthorized PDF uploads or suspicious account activity before patching, credential rotation may not be immediately necessary. However, if your instance was public-facing for any duration while vulnerable, conduct a user access audit and consider rotating credentials for administrative and high-privilege accounts as part of defense-in-depth practice.
Can we disable PDF uploads entirely as a temporary fix?
Yes. Temporarily restricting PDF upload permissions via user groups or disabling the feature entirely in admin settings provides a strong interim control if patching cannot be deployed immediately. This does not address the vulnerability itself but prevents the attack vector from being triggered until a proper patch is applied.
How do we know if we have been exploited?
Search your application and web server logs for suspicious PDF uploads, errors during PDF processing, or unexpected child process spawning. Examine user activity logs for uploads from unexpected accounts. Check file modification timestamps on your Discourse installation directory for unauthorized changes around the time of potential exploitation. If suspected, isolate the instance, preserve logs, and engage your incident response team.
This analysis is provided for informational purposes and should not be construed as legal or compliance advice. Patch version numbers and affected product versions are drawn from official CVE records and vendor advisories as of the publication date. Organizations must verify compatibility and test patches in staging environments before production deployment. The vulnerability's exploitability depends on specific non-default configurations; administrators should audit their own settings to determine actual exposure. SEC.co makes no warranty regarding the completeness or accuracy of this analysis and recommends consulting official vendor documentation and your internal security team for definitive guidance. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2025-41265HIGHWaterfall WF-500 TX Host OS Command Injection (CVSS 7.2)
- CVE-2025-41266HIGHWaterfall WF-500 TX Host Command Injection Vulnerability Analysis
- CVE-2025-41267HIGHWaterfall WF-500 TX Host Command Injection Vulnerability
- CVE-2025-41279HIGHOS Command Injection in Waterfall WF-500 RX Host Administration WebUI
- CVE-2025-41281HIGHWaterfall WF-500 OS Command Injection
- CVE-2025-66273HIGHQNAP Command Injection in QTS and QuTS hero
- CVE-2025-66279HIGHQNAP NAS Command Injection – Admin Authentication Required, HIGH Severity
- CVE-2025-69755HIGHNeterbit NW-431F Router RCE and Data Exposure Vulnerability