How severe is GHSA-7wq5-jgww-5rw3?

No CVSS score has been assigned to GHSA-7wq5-jgww-5rw3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7wq5-jgww-5rw3?

GHSA-7wq5-jgww-5rw3 affects the following packages: discourse (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-7wq5-jgww-5rw3?

Update discourse to 2026.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7wq5-jgww-5rw3 is resolved across your whole dependency graph.

How do I detect GHSA-7wq5-jgww-5rw3 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for discourse. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7wq5-jgww-5rw3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7wq5-jgww-5rw3?

O3 pinpoints whether GHSA-7wq5-jgww-5rw3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7wq5-jgww-5rw3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7wq5-jgww-5rw3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-7wq5-jgww-5rw3?

GHSA-7wq5-jgww-5rw3 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-7wq5-jgww-5rw3 published, and has it been updated?

GHSA-7wq5-jgww-5rw3 was published on July 14, 2026 and was last updated on July 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

GHSA-7wq5-jgww-5rw3

Fix: discourse/discourse@ca5a7e0

GHSA-7wq5-jgww-5rw3 is a OS Command Injection vulnerability in discourse. O3 Security confirms whether GHSA-7wq5-jgww-5rw3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Discourse: Remote code execution via pdf uploads

Also known asCVE-2026-55420

Published

Jul 14, 2026

Updated

Jul 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦discourse

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`discourse`	≥ 2026.1.0&&< 2026.1.5	2026.1.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for discourse. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update discourse to 2026.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7wq5-jgww-5rw3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7wq5-jgww-5rw3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7wq5-jgww-5rw3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-7wq5-jgww-5rw3 in your dependencies?

O3 detects GHSA-7wq5-jgww-5rw3 across Bitnami dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works