CVE-2026-97875 json
DNS rebinding vulnerability in rojo serve HTTP API
published 5mo ago modified last mo. also RUSTSEC-2026-0279 , EUVD-2026-86991
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io rojo 7.7.0
- rojo-rbx rojo 7.7.0
- github.com/rojo-rbx/rojo@ac6941f commit
- github.com/rojo-rbx/rojo#1270 pull request
Is CVE-2026-97875 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | rojo | >=0.0.0-0, <7.7.0 |
7.7.0 |
Affected products
- rojo-rbx rojo
Classification
- Weakness
-
- CWE-350 Reliance on Reverse DNS Resolution for a Security-Critical Action
References
-
github.com
/rojo-rbx/rojo/pull/1270
patch, web
-
github.com
/rojo-rbx/rojo/commit/ac6941f05483b0875fda52c7664cd42033db7fa2
web
-
rustsec.org
/advisories/RUSTSEC-2026-0279.html
vendor-advisory, advisory
-
osv.dev
/vulnerability/RUSTSEC-2026-0279
related
-
crates.io
/crates/rojo
package
Sources
- CVE List CVE-2026-97875
- NVD CVE-2026-97875
- OSV RUSTSEC-2026-0279
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.