CVE-2026-97875

DNS rebinding vulnerability in rojo serve HTTP API

  • High 8.1

Description

Rojo's "rojo serve" HTTP API (default port 34872) has no Host/Origin header validation, making it vulnerable to DNS rebinding. A malicious webpage can read all project source, write malicious code to files on disk, and launch local programs via opener::open() with no user interaction beyond visiting the page.

Key facts

Published
25 Sep 2026
Last changed
25 Sep 2026
Assigned by
redhat-cnalr
EPSS
0.26% likely to be exploited in the next 30 days, higher than 17.821% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 8.1CVSS 3.1, Highfrom the CNA (redhat-cnalr)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
rojo-rbxrojo
  • Default status: unaffected
  • 0 up to but excluding 7.7.0 (affected)

Timeline

  1. 2 Jun 2026 Reported
  2. 3 Jun 2026 Maintainers confirmed
  3. 7 Jun 2026 Fix merged
  4. 2 Jul 2026 Released in 7.7.0
  5. 25 Sep 2026 Published

Weakness

References