CVE-2026-46413

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
28.8%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 14, 2026

Advisory Details (5)

Auto-updated Jul 9, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Regular users can route multipart uploads into the admin backup store · Advisory · discourse/discourse · GitHub

https://github.com/discourse/discourse/security/advisories/GHSA-3mvf-q9rg-w6m7
github_commit

commit abaa664c5df8 (discourse/discourse)

Fix landed in discourse/discourse commit abaa664c5df8 — awaiting tagged release

https://github.com/discourse/discourse/commit/abaa664c5df84026efb2ca264ba0f5586c3f2b01
github_commit

commit a53df26dcf7e (discourse/discourse)

Fix landed in discourse/discourse commit a53df26dcf7e — awaiting tagged release

https://github.com/discourse/discourse/commit/a53df26dcf7e50ce2b20bfd5454a0c9d44b8fc7d
github_commit

commit 7ddde266617b (discourse/discourse)

Fix landed in discourse/discourse commit 7ddde266617b — awaiting tagged release

https://github.com/discourse/discourse/commit/7ddde266617b452152c1bf5f903f6c07be38fc40
github_commit

commit 1f1ded8dd361 (discourse/discourse)

Fix landed in discourse/discourse commit 1f1ded8dd361 — awaiting tagged release

https://github.com/discourse/discourse/commit/1f1ded8dd361d81786bff17b35e1138d6ee299c0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-15 01:06 UTCEG score recompute
  4. 2026-07-14 00:31 UTCEG score recompute
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 23:56 UTCEG score recompute
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 23:21 UTCEG score recompute
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-10 22:46 UTCEG score recompute
  12. 2026-07-09 22:11 UTCEG score recompute
  13. 2026-07-09 22:10 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46413?
CVE-2026-46413 is a medium vulnerability published on July 9, 2026. 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.
When was CVE-2026-46413 disclosed?
CVE-2026-46413 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46413 actively exploited?
CVE-2026-46413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46413?
CVE-2026-46413 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-46413?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46413, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46413

Explore →

Is Your Infrastructure Affected by CVE-2026-46413?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs