# CVE-2026-97875: DNS rebinding vulnerability in rojo serve HTTP API

> Attackers can exploit DNS rebinding in Rojo's HTTP API to read source code, modify files, and execute local programs via a malicious webpage.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** RUSTSEC-2026-0279

## What is CVE-2026-97875?

CVE-2026-97875 is a high-severity server-side request forgery vulnerability in rojo-rbx rojo, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-350 (Reliance on Reverse DNS Resolution for a Security-Critical Action)

## Which versions are affected by CVE-2026-97875?

1 open source package ship an affected version, including rojo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rojo` | crates.io | From 0.0.0-0 | 7.7.0 |

## How do I fix CVE-2026-97875?

Upgrade rojo to 7.7.0 or later.

## Is CVE-2026-97875 being exploited?

There is no known exploitation of CVE-2026-97875 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97875 and fix it if it is affected.

What it is: CVE-2026-97875 is a high-severity server-side request forgery vulnerability in rojo-rbx rojo, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-97875 in the wild and no public exploit code.

Affected packages and fixed versions:
- rojo (crates.io): affected from 0.0.0-0; fixed in 7.7.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97875/ (Markdown: https://insights.sbomify.com/CVE-2026-97875/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97875
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97875
- OSV: https://osv.dev/vulnerability/CVE-2026-97875

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97875/
Summaries are generated and may contain mistakes; the official description above is the record.