Loading...
Skip to main content

CVE-2026-97875 — Vulnerability in rojo — CVE Details

HIGH

Rojo development server vulnerable to DNS rebinding, allowing unauthenticated read/write access and local program execution

Published June 2, 2026Updated September 25, 2026Source: osv

Summary

Rojo's `rojo serve` command starts an unauthenticated HTTP API on localhost (default port 34872) with no `Host` or `Origin` header validation. While direct cross-origin `fetch()` requests from a malicious website are blocked by the browser's default CORS policy, an attacker can use DNS rebinding to bypass this restriction entirely. The serve API is a two-way sync protocol. Once a DNS rebind is established, a malicious webpage visited by a developer running `rojo serve` can, without any further user interaction: - **Read the full project source:** `GET /api/rojo` returns the session ID, root instance ID, and project name. `GET /api/read/{id}` enumerates the complete instance tree including all script contents, exposing proprietary game logic, configuration, and any secrets embedded in source files. - **Write to project files on disk:** `POST /api/write` pushes changes back through Rojo's sync pipeline, allowing an attacker to inject arbitrary Lua into the developer's project. If the developer then publishes their game, the injected code executes on every player's client — a supply chain attack vector. - **Launch local programs:** `POST /api/open/{id}` calls the OS-level `opener::open()` function, which invokes the platform's default handler (`open` on macOS, `xdg-open` on Linux, `start` on Windows) for the target file. Exploitation requires only that `rojo serve` is running (the standard Roblox development workflow) and that the developer visits an attacker-controlled webpage in any browser on the same machine. The port is a fixed well-known default (34872), there is no authentication, and no user interaction is needed beyond the initial page visit. The flaw was corrected in [#1270](https://github.com/rojo-rbx/rojo/pull/1270), which adds `Host`/`Origin` header validation to reject cross-origin requests, gates `/api/open` to loopback clients regardless of validated origin, and emits a warning when the server binds to a non-loopback address Reported by [Aiden Mohan](https://github.com/AidenMohan).

Advisory Timeline

  • First published June 2, 2026 (132 days ago).
  • Last revised September 25, 2026 — 115 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Cargo
Update rojo to 7.7.0 or later
cargo update -p rojo --precise 7.7.0

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: crates.io (1).

PackageEcosystemAffectedFixed In
rojo
crates.io
All versions7.7.0

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Frequently Asked Questions

What is CVE-2026-97875?
Rojo development server vulnerable to DNS rebinding, allowing unauthenticated read/write access and local program execution This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.1/10).
How do I check if my project is affected by CVE-2026-97875?
CVE-2026-97875 affects rojo. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-97875 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.1

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

RUSTSEC-2026-0279

Related CVEs

  • CVE-2026-93657
    HIGH

    hickory-resolver: Resolver::lookup() and Resolver::lookup_ip() APIs obscure DNSSEC validation failures

  • CVE-2026-18140
    HIGH

    aws-smithy-json: Uncontrolled recursion in the aws-smithy-json unknown-key skip path allows unauthenticated remote denial of service in smithy-rs generated servers

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies