Read the docs

Path traversal in Discourse backup restore copies files to S3

Priority MEDIUM 46CWE-22Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Information disclosure
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · GHSA-c82j-5rvx-w25m. Fix status from GitHub. Impact type from CWE-22 and the CVSS impact.

Summary

Discourse versions from 2026.7.0-latest before 2026.7.5, from 2026.9.0-latest before 2026.9.2, and from 2026.10.0-latest before 2026.10.1 are affected. A crafted backup with unsafe upload file names makes a restore copy files from outside the uploads directory into the S3 bucket, including configuration files (CWE-22). An attacker with high privileges can exploit this when a site has allow_restore enabled and restores such a backup.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Impact When a crafted backup is restored on a site using S3, its upload file names can make Discourse upload files from outside the uploads directory to the bucket, including configuration files. Only sites with `allow_restore` enabled are affected. ### Workarounds Keep `allow_restore` disabled, and only restore backups from trusted sources. Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-4U20ZJW5.

Why it matters now

Fix Fixed Discourse: 2026.11.0-latest.1, 2026.10.1, 2026.9.2 +1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Discourse—2026.11.0-latest.1Patch availableGHSA-c82j-5rvx-w25m
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-c82j-5rvx-w25m
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-c82j-5rvx-w25m
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-c82j-5rvx-w25m
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-c82j-5rvx-w25m
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-c82j-5rvx-w25m
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-c82j-5rvx-w25m
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-c82j-5rvx-w25m

Remediation

Upgrade Discourse to 2026.11.0-latest.1, 2026.10.1, 2026.9.2, or 2026.7.5, depending on the release line in use. Until then, keep allow_restore disabled and only restore backups from trusted sources.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-c82j-5rvx-w25m Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-c82j-5rvx-w25m Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-c82j-5rvx-w25m Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-c82j-5rvx-w25m Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-c82j-5rvx-w25m

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences