dbcve.org
DiscourseApplication

CVE-2026-46413

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 2026.1.5 / 2026.4.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Discourse is an open-source discussion platform. Prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5, regular users could route direct S3 multipart uploads through ExternalUploadManager into the admin backup store. This issue is fixed in versions 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-862

The application checks who you are but not whether you're allowed to perform a given action, so any authenticated user can reach things meant for others. This is the classic “change the ID in the URL” bug. The fix is an authorization check on every request, evaluated against the acting user's permissions.

General guidance for the missing authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DiscourseApplication
Affected:>= 2026.1.0, < 2026.1.5>= 2026.4.0, < 2026.4.2>= 2026.5.0, < 2026.5.1= 2026.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.1.5 / 2026.4.2 / 2026.5.1 or later
Fixed in 2026.1.52026.4.22026.5.1
Vendor patch github.com →
Recommended fix High confidence

2026.6.0 (or 2026.5.1, 2026.4.2, or 2026.1.5 depending on your version branch)

  1. 1. Identify the current Discourse version by checking the admin dashboard or running `git describe --tags` in the Discourse directory
  2. 2. Based on the current version branch, upgrade to the appropriate fixed version:
  3. - If running 2026.1.x: upgrade to 2026.1.5
  4. - If running 2026.4.x: upgrade to 2026.4.2
  5. - If running 2026.5.x: upgrade to 2026.5.1
  6. - If running 2026.6.0: upgrade to 2026.6.0 (this version contains the fix)
  7. 3. Follow standard Discourse upgrade procedures: backup the database, stop the application, pull the new version, run bundle install, run rake db:migrate, and restart the application
  8. 4. Verify the upgrade was successful by checking the version in the admin dashboard
Caveat Standard Discourse upgrade risks apply - review release notes for any breaking changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46413 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46413 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data