High
DNS rebinding vulnerability in rojo serve HTTP API
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.
Announced Source revision 1
Original source ↗CVE-2026-97875
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-97875
rojo
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "rojo-rbx",
"product": "rojo",
"versions": [
{
"status": "affected",
"version": "0",
"lessThan": "7.7.0",
"versionType": "semver"
}
],
"packageName": "rojo",
"collectionURL": "https://crates.io",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-97875
Source reference:
/cveMetadata/cveId
Publisher severity
high
Source reference: /containers/cna/metrics
- Event
- #2185 · Revision 1
- Added to Heist Feed
- Publisher date