Skip to main content
VulnerabilityPublished Updated

CVE-2025-64388: Circutor TCPRS1plus · Uncontrolled Resource Consumption

Affects Circutor TCPRS1plusSource CVE Database V5

0

Not known to be exploited · CVSS 9.2 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Circutor TCPRS1plusAffected
  • =1.0.14
Fixed in–

AI-suggested

  1. Immediately implement network segmentation to isolate TCPRS1plus devices from general IT networks and restrict access to trusted management hosts only.
  2. Deploy firewall rules and intrusion prevention systems (IPS) to detect and block malformed or suspicious protocol requests targeting the device's web server.
  3. Monitor network traffic for unusual spikes or repeated requests that could indicate exploitation attempts.
  4. Engage with Circutor support channels to obtain information on patches or firmware updates addressing this vulnerability and apply them as soon as they become available.
  5. Conduct regular vulnerability assessments and penetration testing focused on OT devices to identify and remediate similar issues proactively.
  6. Implement strict access controls and logging on management interfaces to detect unauthorized access attempts.
  7. Develop and test incident response plans specific to OT environments to minimize downtime in case of exploitation.
  8. Consider deploying redundancy or failover mechanisms for critical devices to maintain availability during attacks or maintenance.

Description

Denial of service of the web server through specific requests to this protocol

References

Community reviews

Loading reviews…