How severe is CVE-2026-97875?

CVE-2026-97875 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-97875 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-97875?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-97875 published?

CVE-2026-97875 was published on 2026-09-25 and last updated on 2026-09-30.

CVE-2026-97875

CVE-2026-97875 is a high-severity vulnerability with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-350.

Key facts

Severity: High (CVSS 3.x base score 8.1)
EPSS exploit prediction: 0% (16th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-350
Published: 2026-09-25
Last modified: 2026-09-30

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.

Frequently asked questions

What is 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 the page.
How severe is CVE-2026-97875?: CVE-2026-97875 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-97875 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-97875?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-97875 published?: CVE-2026-97875 was published on 2026-09-25 and last updated on 2026-09-30.

References

Other CWE-350 vulnerabilities

CVE-2026-1490 — Critical (CVSS 9.8): The Spam protection, Anti-Spam, FireWall by CleanTalk plugin for WordPress is vulnerable to unauthorized Arbitrary…
CVE-2026-61568 — Critical (CVSS 9.6): `@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Versions prior to 2.1.30 expose the Streamable…
CVE-2023-52235 — High (CVSS 8.8): SpaceX Starlink Wi-Fi router GEN 2 before 2023.53.0 and Starlink Dish before 07dd2798-ff15-4722-a9ee-de28928aed34 allow…
CVE-2026-55526 — High (CVSS 8.5): PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.58, spider_tools._host_is_blocked() does not…
CVE-2025-8036 — High (CVSS 8.1): Thunderbird cached CORS preflight responses across IP address changes. This allowed circumventing CORS with DNS…
CVE-2026-56709 — High (CVSS 7.5): Grav before 3.9.2 fails to validate untrusted Host headers in the sendInvitationEmail() function when constructing…

Browse all CWE-350 vulnerabilities →