CVE-2026-97875
Received Received - Intake

Rojo Serve HTTP API DNS Rebinding Vulnerability

Publication date: 2026-09-25

Last updated on: 2026-09-25

Assigner: redhat-cnalr

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-25
Last Modified
2026-09-25
Generated
2026-09-25
AI Q&A
2026-09-25
EPSS Evaluated
N/A
NVD
CVE-2026-97875
EUVD
EUVD-2026-86991

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-350 The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Rojo's 'rojo serve' HTTP API lacks Host/Origin header validation, allowing DNS rebinding attacks. This means a malicious webpage can interact with the API to read project source code, modify files on disk, and execute local programs without further user interaction beyond visiting the page.

Detection Guidance

Check if Rojo's HTTP API (default port 34872) is running on your network. Use commands like 'netstat -tuln | grep 34872' or 'ss -tuln | grep 34872' to detect listening services on that port. Inspect network traffic for unvalidated Host/Origin headers.

Impact Analysis

An attacker could exploit this to steal sensitive project files, inject malicious code into your system, or run unauthorized programs. Visiting a compromised webpage could lead to data theft, system compromise, or further network intrusions without additional user actions.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's data protection principles or HIPAA's safeguards for protected health information. Organizations may face compliance breaches, legal penalties, and reputational damage if exploited.

Mitigation Strategies

Disable or restrict access to Rojo's HTTP API (port 34872) via firewall rules. Implement Host/Origin header validation if possible. Avoid running Rojo in untrusted environments. Monitor for unauthorized file writes or program launches.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-97875. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart