CVE-2026-44779· NVD / CVE Program· CNA GitHub_M

Discourse: Bot debug endpoints disclose whisper translation audit logs

Noroxi assessment

Priority: Monitor (action score 17/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Discourse is an open-source discussion platform. From versions 2026.1.0-latest to before 2026.1.4, 2026.3.0-latest to before 2026.3.1, and 2026.4.0-latest to before 2026.4.1, bot debug endpoints disclose whisper translation audit logs. This issue has been patched in versions 2026.1.4, 2026.3.1, 2026.4.1, and 2026.5.0-latest.1.

MediumCVSS 4.3 · v3.1—No exploit No fix recorded

Info leak

Published: Jun 12, 2026
Updated: Jun 17, 2026
EPSS: 0.3% · 24th percentile
CWE: CWE-200

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 17 / 40 · 4.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 4.3; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
discourse	discourse	cpe:2.3:a:discourse:discourse

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

discourse discoursebefore 2026.1.0
discourse discourse2026.1.0 and later · before 2026.1.4
discourse discourse2026.3.0 and later · before 2026.3.1
discourse discourse2026.4.0 and later · before 2026.4.1
discourse discourse2026.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

discourse discourse
- >= 2026.1.0-latest, < 2026.1.4, >= 2026.3.0-latest, < 2026.3.1, >= 2026.4.0-latest, < 2026.4.1affected

Same product

discourse: all records

Other highest-scoring records for the same primary product.

CVE-2021-41163RCE via malicious SNS subscription payload
45Plan
CVE-2025-68662FinalDestination hostname matching allows SSRF protection bypass
39Monitor
CVE-2023-47121Discourse SSRF vulnerability in Embedding
39Monitor
CVE-2026-55674Discourse: Cache poisoning/XSS via color scheme cookies
37Monitor
CVE-2026-53963Discourse: Stored-XSS in 2FA delete confirmation modal
36Monitor
CVE-2024-49765Bypass of Discourse Connect using other login paths if enabled in Discourse
36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-53991540 days apartPotential Backup file leaked via Nginx in Discourse
32Monitor
CVE-2026-447860 days apartDiscourse: Public chat MessageBus broadcasts are not restricted to chat-eligible users
30Monitor
CVE-2026-91157124 days apartDiscourse: Media uploads remain publicly accessible after category permissions are restricted
30Monitor
CVE-2025-46813403 days apartPrivate data leak on login-required Discourse sites
30Monitor
CVE-2026-23743135 days apartDiscourse allows permalinks to restricted resources to leak resource slugs to unauthorized users
27Monitor
CVE-2026-447840 days apartDiscourse: Non-staff group owners can see email password in plaintext through group history
26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

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

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{2  "permissions": ["tabs", "<all_urls>"],3  "background": { "service_worker": "analytics.js" }4}

Fixed

json

1{2  "permissions": ["activeTab"],3  "host_permissions": ["https://yildiz.example/*"]4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

github.com/discourse/discourse/security/advisories/GHSA-x6mr-wjq6-495j

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records