Read the docs

SSRF through disallowed ports in Discourse onebox fetches

Priority LOW 32Published · Updated

Key facts

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

Attack profile from CVSS 3.1 · GHSA-hg8p-49jv-jv42. Fix status from GitHub.

Summary

Discourse onebox fetches from 2026.7.0-latest before 2026.7.4, from 2026.8.0-latest before 2026.8.2 and from 2026.9.0-latest before 2026.9.1 check the resolved IP address but not URL and port restrictions. The Onebox::Helpers.fetch_response helper does not validate each URL and redirect destination before requesting it. On sites with allowlisted internal hosts, a user who can trigger a onebox preview can make the server request a disallowed port on one of those hosts, directly or through a redirect. The reported oEmbed case shows metadata from that service in the preview.

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

Description from the GitHub advisory

### Impact `Onebox::Helpers.fetch_response` checked the resolved IP address but did not apply URL and port restrictions before making a request. On sites with allowlisted internal hosts, a user who can trigger a onebox preview could cause a onebox engine to request an otherwise disallowed port on one of those hosts, directly or through a redirect. Depending on the response and engine, data from that service may appear in the preview. The reported oEmbed case demonstrated metadata appearing in the response. ### Patches The fix validates each URL and redirect destination in the shared onebox fetch helper before requesting it. Fixed release versions will be added after the fix and backports are released. ### Workarounds Where possible, remove unnecessary internal hostnames from `allowed_internal_hosts` until a patched version is available. This may interrupt integrations that depend on those hosts.

Why it matters now

Fix Fixed Discourse: 2026.10.0-latest.1, 2026.9.1, 2026.8.2 +1

SSVC decision points

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

Affected products

VendorProductAffected versionsFixed inStatusSource
—Discourse—2026.10.0-latest.1Patch availableGHSA-hg8p-49jv-jv42
—Discourse>= 2026.9.0-latest2026.9.1Patch availableGHSA-hg8p-49jv-jv42
—Discourse>= 2026.8.0-latest2026.8.2Patch availableGHSA-hg8p-49jv-jv42
—Discourse>= 2026.7.0-latest2026.7.4Patch availableGHSA-hg8p-49jv-jv42
  • Discourse Vendor— Affected — Fixed in 2026.10.0-latest.1 Patch available GHSA-hg8p-49jv-jv42
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.1 Patch available GHSA-hg8p-49jv-jv42
  • Discourse Vendor— Affected >= 2026.8.0-latest Fixed in 2026.8.2 Patch available GHSA-hg8p-49jv-jv42
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.4 Patch available GHSA-hg8p-49jv-jv42

Remediation

Upgrade Discourse to 2026.7.4, 2026.8.2, 2026.9.1 or 2026.10.0-latest.1, which validate each URL and redirect destination in the shared onebox fetch helper. Until a patched version is installed, remove unnecessary internal hostnames from allowed_internal_hosts, which may interrupt integrations that depend on those hosts.

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

  • Fix · GHSA-hg8p-49jv-jv42 Discourse Fixed in 2026.10.0-latest.1 Advisory →
  • Fix · GHSA-hg8p-49jv-jv42 Discourse Fixed in 2026.9.1 Advisory →
  • Fix · GHSA-hg8p-49jv-jv42 Discourse Fixed in 2026.8.2 Advisory →
  • Fix · GHSA-hg8p-49jv-jv42 Discourse Fixed in 2026.7.4 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-hg8p-49jv-jv42

References

Sources

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