Vulnerability Watch

What Ray is: Ray is an open-source Python framework used by developers and data scientists to run large AI and machine learning workloads across many computers at once.

What it is: A critical flaw in Ray allows an attacker to execute arbitrary code (RCE — remote code execution, meaning running any command they choose on your machine) through a browser-based DNS rebinding attack (where a malicious website tricks your browser into making requests on your behalf to software running locally on your own machine).

Who's at risk: Developers running Ray in development or testing environments, particularly those using Firefox or Safari.

CVSS: 9.4 (Critical — patch today.)

Root cause: Ray's development team has not implemented authentication on critical internal endpoints, including /api/jobs. Because these endpoints accept requests from browsers without verifying who is asking, and because the User-Agent header can be freely modified by a webpage, an attacker-controlled site can manipulate a browser into sending commands directly to Ray as if it were the legitimate user.

Attack vector: A developer visits a malicious website or is served a malicious ad while Ray is running locally. The page performs a DNS rebinding attack, redirecting the browser to Ray's unauthenticated API. The attacker submits a crafted job request, and Ray executes it with the developer's own system privileges. The attack can also reach Ray instances running inside a private corporate network by using the victim's browser as an unwitting intermediary. The RondoDox DDoS botnet incorporated this vulnerability two days before public disclosure in November 2025, and a separate campaign (ShadowRay 2.0) has used unpatched Ray instances to build a cryptocurrency mining botnet.

Detection strategies: Check Ray job logs for unexpected job submissions, particularly shell commands or curl-based install scripts. Look for outbound network requests from Ray processes to unfamiliar external addresses. Monitor for new or modified files in home directories on machines where Ray is running.

Recommended actions:

1. Upgrade Ray to version 2.52.0 immediately — FCEB agencies must patch by 20 August 2026.
2. Restrict Ray dashboard and API ports to localhost only; do not expose them on a network interface.
3. Avoid browsing untrusted websites while Ray is running locally.

No notable new vulnerability disclosed in the last 24 hours.

The Evooo1Bot botnet (covered in the AI & Emerging Threats section above) exploits a collection of previously known flaws across multiple device brands rather than a single newly disclosed CVE. No qualifying new CVE appears in today's brief.

CVE ID not confirmed in source — check the original advisory before acting.

What Evooo1Bot targets: Home routers, enterprise networking equipment, and IoT (Internet of Things — everyday devices connected to the internet, like smart routers and remote-terminal units) running Linux-based firmware.

What it is: Evooo1Bot is a new botnet — a network of hijacked devices secretly controlled by an attacker — built on leaked source code from the notorious Mirai malware. Researchers at Fortinet's FortiGuard Labs identified it after seeing coordinated attacks on edge devices across multiple regions since July 2026, as reported by Infosecurity Magazine.

Who's at risk: Anyone running an unpatched router or internet-connected device from brands including D-Link, NETGEAR, Tenda, and Telesquare, particularly where the device's admin interface is exposed directly to the internet.

CVSS: Not yet scored for the botnet itself — treat as High until confirmed.

Root cause: The botnet exploits known, unpatched vulnerabilities in edge devices — some dating back to 2007. Manufacturers issued fixes, but many devices in the field were never updated, leaving attackers with a large pool of targets to automate against.

Attack vector: Evooo1Bot scans the internet for vulnerable devices, fires exploit payloads at them, and once inside, installs a persistent agent. That agent connects back to attacker-controlled infrastructure and — most significantly — activates a SOCKS relay module that turns the compromised device into a proxy, concealing the attacker's real location while routing further attacks through the victim's network.

Recommended actions:

1. Log into your router's admin panel and apply any available firmware updates immediately.
2. Disable remote management interfaces unless you specifically need them — check your router settings for "Remote Access" or "WAN Management" and turn them off.
3. If your router model appears in the article (D-Link, NETGEAR, Tenda, Telesquare), check the manufacturer's support page for a patch or end-of-life notice.

What VMware vCenter Server is: Centralised IT management software that lets organisations control, monitor, and configure all their virtual machines and servers from a single platform.

What it is: A directory traversal flaw (a weakness that lets an attacker request files outside the intended folder structure) in vCenter's Syslog server component, leading to remote code execution (RCE — running attacker-supplied commands on the target machine).

Who's at risk: Any organisation with a vCenter server reachable over the network. No login is required to trigger the flaw.

CVSS: 9.8 (Critical — patch today).

Root cause: The Syslog server component fails to validate file path inputs, allowing a crafted request to escape the intended directory and reach sensitive system areas. There are no workarounds. Only patching resolves it.

Attack vector: An attacker with network access sends a specially crafted request to the vCenter Syslog server. The server processes the malformed path without restriction, granting file access and enabling arbitrary code execution. In active exploitation, attackers then drop the reverse_ssh tool, which phones home to attacker infrastructure, bypassing inbound firewall rules.

Detection strategies:

1. Look for unexpected outbound SSH connections from vCenter hosts to unknown external IPs.
2. Search for reverse_ssh binaries using QUIRSO's published YARA rule — but validate any hits, as the tool also has legitimate uses.
3. Check for new, unrecognised processes running under the vCenter service account.

Recommended actions:

1. Apply the emergency patch immediately: 9.1.0.0300, 9.0.2.0100, 8.0 U3k, or 8.0 U2f.
2. Restrict network access to vCenter — it should never be publicly internet-facing.
3. Review outbound connection logs for traffic to unfamiliar infrastructure since August 3.

What Adobe ColdFusion is: ColdFusion is Adobe's web application server platform, used by developers to build and host database-driven websites and internal business applications.

What it is: This is an OS command injection vulnerability (a flaw where an attacker can feed specially crafted input that the server executes as a system-level command, rather than treating it as ordinary data). It carries a CVSS score of 10.0 and can lead to arbitrary code execution on the host server.

Who's at risk: Any organisation running ColdFusion versions prior to 2025.0.12 or 2023.0.23 with internet-accessible deployments. Adobe rates this Priority 1, meaning active targeting is considered likely.

CVSS: 10.0 (Critical — patch today. Stop reading, go patch.)

Root cause: The application fails to sanitise user-supplied input before passing it to underlying operating system functions. An attacker can craft a request containing shell commands that the server interprets and executes with its own privileges, bypassing application-layer controls entirely.

Attack vector: An attacker sends a malicious request to an exposed ColdFusion endpoint, embedding OS commands inside a parameter the server processes unsafely. The server executes those commands directly, potentially allowing the attacker to install malware, create new administrative accounts, or move laterally (pivot from one compromised system to reach other machines on the same network) through internal infrastructure.

Detection strategies: Look for unusual child processes spawned from the ColdFusion application server process (e.g. cmd.exe or /bin/sh). Review web server access logs for malformed or unexpectedly long parameter strings in POST requests. Monitor for new user accounts or scheduled tasks created around the time of any suspicious ColdFusion traffic.

Recommended actions:

1. Update ColdFusion to version 2025.0.12 or 2023.0.23 immediately.
2. Restrict external access to ColdFusion admin and API endpoints at the firewall or reverse proxy level.
3. Enable application-level logging and alert on unexpected process spawning from the ColdFusion service account.

CVE ID not confirmed in source — check the original advisory before acting.

What SAP Commerce Cloud is: An enterprise e-commerce platform used by large retailers and manufacturers to manage online storefronts, product catalogues, and customer data.

What it is: A maximum-severity flaw caused by missing authorisation checks and insufficient input validation. An attacker with no account can send crafted requests to vulnerable internal functions and run arbitrary code on the server.

Who's at risk: Any organisation running an unpatched SAP Commerce Cloud (Data Hub Adapter) instance. If the endpoint is reachable — even internally — the risk is real.

CVSS: 10.0 (Critical). Patch today.

Root cause: SAP's Data Hub Adapter ships with a default authentication client that fails to enforce proper access controls. Functions downstream of that client do not validate the input they receive, meaning an unauthenticated request can reach and trigger code execution directly.

Attack vector: An attacker with network access to the endpoint sends specially crafted input through the default authentication client, bypassing authorisation entirely. Because the affected functions lack validation, that input reaches execution-level components. No credentials are needed. The attacker gains the ability to run any command on the host system.

Detection strategies: Look for unexpected outbound connections from the Commerce Cloud host. Review authentication logs for requests hitting Data Hub Adapter endpoints from unknown sources. Alert on processes spawned by the Commerce Cloud service account that do not match normal application behaviour.

Recommended actions:

1. Apply SAP's August 2026 patch and redeploy the updated Commerce Cloud version immediately.
2. As a temporary measure until patching is complete, configure an IP Filter Set to restrict access to the vulnerable endpoint to trusted sources only.
3. Review network exposure — this endpoint should never be reachable from the public internet.

What Progress Kemp LoadMaster is: LoadMaster is an application delivery controller and load balancer used by enterprises and government agencies worldwide to distribute web traffic across multiple servers and keep applications running reliably. Progress Software reports over 100,000 deployments, including across 80% of Fortune 500 companies.

What it is: A command injection flaw (a class of bug where an attacker can slip operating system commands into a field that should only accept data) in LoadMaster's API lets unauthenticated attackers run arbitrary commands on the appliance. No account, no password, no invitation required.

Who's at risk: Any organisation running an unpatched LoadMaster instance with its management interface reachable from the internet. Shadowserver estimates roughly 300 instances are currently exposed online.

CVSS: Critical — patch today. Stop reading, go patch.

Root cause: The API endpoints on LoadMaster failed to sanitise (properly clean and validate) inputs before passing them to underlying system commands. Think of it like a form on a website that accepts your name and then passes whatever you type directly into a command the server runs — if you type a name followed by a system instruction, both get executed. Progress released a fix in June.

Attack vector: An attacker sends a crafted HTTP request to one of the affected API endpoints with a payload (a string of commands) embedded where the application expects clean data. Because no authentication is required and the input is not validated, the server executes the attacker's commands with the privileges of the LoadMaster process. From there, the attacker can read files, install backdoors (hidden persistent access points), or move laterally (pivot from the compromised appliance to other systems on the same network).

Detection strategies: Look for unexpected outbound connections from LoadMaster appliances, particularly to unfamiliar external IPs. Review API access logs for malformed or unusually long input values in command endpoints. Check for new or modified files in system directories, and audit running processes for anything spawned by the LoadMaster service that should not be there.

Recommended actions:

1. Upgrade to GA v7.2.63.2 or LTSF v7.2.54.18 or later immediately — a patch has been available since June.
2. Restrict access to the LoadMaster management interface so it is not reachable from the public internet.
3. Monitor outbound traffic from LoadMaster appliances and alert on any connections to external hosts not in your approved list.

CVE ID not confirmed in source — check the original advisory before acting.

What Connective eID is: A browser extension used by over two million people in Belgium to authenticate their identity and sign documents digitally with their national electronic ID card. It is used by eight of Belgium's ten largest banks and more than 60 government agencies.

What it is: The extension failed to verify which website was allowed to communicate with it. Any website — including one running a malicious ad — could interact with the application without the user knowing.

Who's at risk: Anyone in Belgium who had the extension installed before late July 2026. Exposure required only visiting a compromised or malicious webpage.

CVSS: Not yet scored — treat as High until confirmed.

Root cause: The application did not validate the origin (the source website) of incoming requests. It also allowed web pages to customise the text inside authentication pop-up boxes without displaying which site was making the request. Users had no way to tell a legitimate prompt from a fake one.

Attack vector: A malicious website silently triggers an authentication pop-up using official-looking text. The user enters their PIN, which the extension sends back to the requesting site. The attacker uses that PIN to generate unauthorised approval tokens and forge legally binding electronic signatures whenever the victim's physical eID card is in a card reader. A separate flaw — in how the extension handled local files — allowed remote code execution (RCE — when an attacker runs their own code on someone else's machine) just by having the user visit a webpage after downloading a disguised file.

Detection strategies: Unexpected authentication pop-ups while browsing unfamiliar sites. Unsigned documents appearing in your Belgian government portal history. Any prompt asking for your eID PIN outside of a known, intentional login flow.

Recommended actions:

1. Confirm your Connective eID extension is updated to the late July 2026 release or later.
2. If you signed documents or entered your PIN in the weeks before the patch, report this to your bank and check your CSAM.be account for unexpected activity.
3. Treat any eID PIN prompt on an unfamiliar website as a phishing attempt — cancel and close the tab.

CVE ID not confirmed in source — check the original advisory before acting.

What Atlassian Rovo is: An enterprise AI assistant embedded across Jira, Confluence, and Bitbucket that can autonomously conduct multi-step research tasks and interact with third-party tools including Slack, Microsoft 365, and Google Workspace.

What it is: The RovoBlast flaw let an attacker pre-load instructions into a victim's live Rovo session via a crafted URL. The assistant treated those external instructions as trusted user input and acted on them with the victim's full access permissions.

Who's at risk: Any organisation using Atlassian Rovo with third-party integrations enabled. Users need only click a malicious link while authenticated.

CVSS: Not yet scored — treat as High until confirmed.

Root cause: The rovoChatPrompt URL parameter accepted and pre-filled content into the chat interface without sanitising or flagging its external origin. Rovo's autonomous agent features then executed whatever instructions appeared, since nothing distinguished attacker-supplied input from legitimate user requests. The organisation ID field could even be left blank, and Atlassian's routing still directed the request into the victim's own account.

Attack vector: An attacker crafts a URL embedding malicious instructions via rovoChatPrompt and sends it to an authenticated Rovo user. On click, Rovo loads the instructions silently. Its built-in ResearchAgent then queries connected data sources — Jira, Confluence, SharePoint — and pushes the results to an attacker-controlled external server, completing exfiltration (the unauthorised transfer of data outside an organisation) with no further user interaction required.

Detection strategies: Review Rovo activity logs for outbound URL requests to unfamiliar external domains. Look for ResearchAgent sessions that were not initiated by a recognisable internal workflow. Flag any Rovo session that accessed multiple data sources — Jira plus Confluence plus SharePoint — in rapid, automated succession.

Recommended actions:

1. Confirm the server-side fix is active on your Atlassian instance (Atlassian deployed it July 8, 2026).
2. Restrict Rovo's integration scope — remove access to any data source not actively in use.
3. Disable autonomous browsing and multi-step agent features unless operationally required.

CVE ID not confirmed in source — check the original advisory before acting.

What Cisco IOS XE is: The operating system that runs on a wide range of Cisco routers and switches used in corporate and government networks worldwide.

What it is: A command injection flaw (a bug where an attacker can sneak operating system commands into input fields the software was not designed to handle that way) in Cisco IOS XE Software, scoring 9.8 out of 10.

Who's at risk: Organisations running Cisco IOS XE in autonomous or controller mode on affected versions. Cisco says no active exploitation is known, but at CVSS 9.8, that window will not stay open long.

CVSS: 9.8 — Critical. Patch today.

Root cause: The software fails to properly neutralise special characters in user-supplied input. An attacker can inject commands that the underlying operating system executes directly, bypassing the intended application layer entirely.

Attack vector: An attacker submits crafted input containing operating system commands to the affected interface. The software processes it without stripping the dangerous characters, passes the payload to the OS, and executes it. Depending on privilege level, this could mean full device compromise from a remote connection.

Detection strategies: Look for unexpected process spawns from the IOS XE management interface in system logs. Monitor for unfamiliar outbound connections from network devices. Alert on any administrative commands executed outside of normal change windows.

Recommended actions:

1. Upgrade to a fixed IOS XE release: 17.9.10, 17.12.8, 17.15.6, 17.18.4, or 26.1.2
2. Restrict management interface access to trusted IP ranges only
3. Enable logging on all management plane activity and review alerts daily until patched