CyberSecBulletin
CVE-2026-97875NVD status: Deferred

rojo: Reliance on Reverse DNS Resolution for a Security-Critical Action

CVE-2026-97875 is a high-severity reliance on reverse DNS resolution for a security-critical action vulnerability in rojo from Rojo-rbx, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 7.7.0 as the first without the flaw, so updating rojo to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.26% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update rojo to 7.7.0 or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  3. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
Rojo-rbxrojobefore 7.7.07.7.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N. Scored by CNA.

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Reliance on Reverse DNS Resolution for a Security-Critical Action

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.

How developers prevent this class of flaw

  • Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate.
  • Perform proper forward and reverse DNS lookups to detect DNS spoofing.

More Reliance on Reverse DNS Resolution for a Security-Critical Action vulnerabilities (CWE-350)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Recent Reliance on Reverse DNS Resolution for a Security-Critical Action vulnerabilities

Spotted an error? Tell us.