Read the docs

Moderator can expose secure uploads by setting avatars in Discourse

Priority LOW 35Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-v2gf-jchx-3239. Fix status from GitHub.

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. The avatar management endpoint does not check whether a moderator can view an upload before setting it as another user's avatar. An authenticated moderator can expose a secure private upload owned by another user, which then becomes reachable through the public avatar route.

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

Description from the GitHub advisory

### Impact A privilege escalation and information disclosure vulnerability existed in the user avatar management system. A moderator (a staff user with moderation capabilities) could potentially expose a secure private upload belonging to another user by setting it as that user's avatar. Secure uploads (such as images attached to Private Messages or topics restricted from public view) are protected by access controls that prevent unauthorized users from viewing them directly. However, the avatar management endpoint did not adequately verify if the acting moderator had permission to *view* a specific upload before allowing them to *set* it as another user's avatar. If a moderator set a secure upload (owned by the target user but restricted from the moderator's view) as the target's avatar, the content could become accessible via the public avatar route (`/user_avatar/...`). This bypassed standard security checks, effectively leaking private content to anyone who could access the user's profile or avatar URL. This vulnerability requires an attacker to have Moderator privileges or higher. ### Workarounds No known workarounds for this issue. <!-- patch-triage-lifecycle:4e6497fdfc0f2b41a67107082d96e45ead8ee57443d53ac0439aea658babbef8 --> Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-RE0M74BN.

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-v2gf-jchx-3239
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-v2gf-jchx-3239
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-v2gf-jchx-3239
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-v2gf-jchx-3239
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-v2gf-jchx-3239
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-v2gf-jchx-3239
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-v2gf-jchx-3239
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-v2gf-jchx-3239

Remediation

Upgrade Discourse to 2026.7.5, 2026.9.2, 2026.10.1 or 2026.11.0-latest.1, depending on the release line in use.

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

  • Fix · GHSA-v2gf-jchx-3239 Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-v2gf-jchx-3239 Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-v2gf-jchx-3239 Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-v2gf-jchx-3239 Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-v2gf-jchx-3239

References

Sources

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