CVE-2026-97875

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

CVE-2026-97875

The rojo serve HTTP API (default port 34872 ) is vulnerable to DNS rebinding because it lacks Host/Origin header validation . This flaw allows a malicious webpage to access project source code, write malicious code to the local disk, and execute local programs using opener::open() without user in...

EUVD-2026-86991

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

CVE-2026-97875: Reliance on Reverse DNS Resolution for a Security-Critical Action

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

PT-2026-86907

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 th...

PT-2026-98562

Name of the Vulnerable Software and Affected Versions Rojo affected versions not specified Description The rojo serve command starts an unauthenticated HTTP API on localhost default port 34872 that lacks Host or Origin header validation. This allows an attacker to use DNS rebinding—a technique th...