Vulnerability Watch

What GitLab is: GitLab is a web-based platform that teams use to host, review, and collaborate on software code.

What it is: A path traversal flaw (where an attacker manipulates file path references to reach files they shouldn't be able to access) that lets an unauthenticated user read any file on the GitLab server in a single HTTP request.

Who's at risk: Anyone running a self-hosted GitLab CE or EE instance on an affected version. Cloud-hosted GitLab.com users are already patched.

CVSS: 10.0 (Critical — patch today, ahead of anything else on your list).

Root cause: The server fails to sanitise file path inputs before processing them, allowing a specially crafted request to escape the intended directory and reach arbitrary files — including credentials and configuration secrets.

Attack vector: An attacker sends a POST request to /api/v4/projects/{id}/repository/commits/ with a manipulated file.path parameter. No login required. The server returns the requested file's contents directly.

Detection strategies: Search your logs for POST requests to /api/v4/projects/{id}/repository/commits/ URIs that include file.path parameters. Unexpected hits from external IPs are a strong indicator of exploitation.

Recommended actions:

1. Upgrade to GitLab 19.1.8, 19.2.6, or 19.3.2 immediately
2. If you cannot patch right now, restrict external access to the GitLab API at your firewall
3. Review logs for the pattern above and audit recent access to sensitive configuration files

What Cisco Secure Firewall Management Center is: A centralised management platform used by network administrators to control and monitor Cisco firewall devices across an organisation's infrastructure.

What it is: An authentication bypass vulnerability (a flaw that lets an attacker skip the login process entirely) that allows an unauthenticated remote attacker to execute scripts on the device and gain root access — the highest level of system control — to the underlying operating system.

Who's at risk: Any organisation running an unpatched instance of Cisco Secure FMC that is reachable over a network. Cisco Talos confirms active exploitation in the wild by multiple threat groups, including a ransomware operator and suspected state-sponsored actors. Read the full Talos advisory here.

CVSS: 10.0 (Critical) — patch today. This is the highest possible severity score.

Root cause: The software fails to properly verify a user's identity before allowing access to privileged functions. An attacker can interact with authenticated endpoints without presenting valid credentials, because the application's authentication logic does not enforce the check at the point of execution.

Attack vector: An attacker sends a crafted request directly to the FMC interface without logging in. The application processes the request as though it came from an authorised user, allowing the attacker to execute scripts and establish root-level access. From there, observed post-exploitation activity includes deploying web shells (persistent backdoors hidden in web server files), harvesting stored credentials, and in one confirmed case, deploying a variant of the Cyclops Blink malware previously linked to Russian state actors.

A second related vulnerability, CVE-2026-20316 (CVSS 5.3, Medium), has been used alongside this flaw to further elevate attacker privileges — patch that one too.

Detection strategies: Look for unexpected processes or unfamiliar JAR files in your Tomcat webroot directory. Review authentication logs for access to privileged endpoints from unauthenticated sessions. Monitor for outbound connections to unusual external IP addresses initiated by the FMC process.

Recommended actions:

1. Apply Cisco's available hotfix for CVE-2026-20079 immediately — do not wait for the comprehensive hardening release scheduled for the week of 14 September.
2. Restrict FMC management interface access to trusted IP ranges only.
3. Review FMC access logs for signs of compromise before and after patching.

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

What Adobe Commerce / Magento is: Adobe Commerce, built on the open-source Magento platform, is the software that powers the checkout, product catalogue, and payment processing for thousands of online shops worldwide.

What it is: A zero-day (a flaw with no patch available yet) vulnerability nicknamed StyleSmuggler allows attackers to inject malicious PHP code — the programming language Magento uses behind the scenes — through the platform's template system. No user interaction is required for the attack to succeed.

Who's at risk: Any merchant running Adobe Commerce or Magento versions 2.4.7, 2.4.8, or 2.4.9, including those who applied the July and August 2026 security patches.

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

Root cause: Magento's template engine fails to adequately sanitise input passed through a site's styling properties. An attacker exploits this by deliberately generating a payment failure report, which causes Magento to execute injected code when the platform sends a "Payment Transaction Failed Reminder" email. The flaw exists because the email-rendering process trusts template content that should be treated as untrusted input.

Attack vector: An attacker submits a crafted request that triggers a payment failure on the targeted store. Magento generates an error report and queues a notification email. When Magento processes that email — including if delivery fails — it executes the attacker's injected PHP code. A Rust-written backdoor is then installed on the server, disguised as a system process name such as [kworker/u:8:0] or fc-cache, and begins communicating with an attacker-controlled server while masquerading as routine NTP (time synchronisation) network traffic.

Detection strategies: Watch for unexpected bursts of "Payment Transaction Failed Reminder" emails from your Magento installation. Look for unfamiliar process names such as [kworker/u:8:0] or fc-cache on your server, particularly ones making outbound connections. Review server logs for unusual NTP traffic patterns — legitimate NTP traffic does not carry system information like hostnames or memory usage.

Recommended actions:

1. Apply Adobe's scheduled Patch Tuesday update on 8 September 2026 and monitor Adobe's official advisory for a specific StyleSmuggler fix.
2. Until a patch is available, consider blocking outbound connections from your Commerce server to unknown external IPs at the firewall level.
3. Alert your hosting provider or server administrator to the active exploitation and ask them to review process lists and outbound traffic immediately.

What SonicWall SMA 1000 is: A remote access gateway used by organisations to let employees connect securely to corporate networks from outside the office.

What it is: CVE-2026-83548 is a pre-authentication SSRF (server-side request forgery — where an attacker tricks the server into making requests on their behalf) flaw in the user-facing portal. No login is required to trigger it.

Who's at risk: Any organisation running an affected SMA 1000 appliance exposed to the internet. Models 6210, 7210, and 8200v on the affected firmware versions are vulnerable. Exploitation is confirmed and ongoing.

CVSS: 10.0 (Critical — patch today, before anything else).

Root cause: The flaw exists because the appliance does not properly restrict which internal resources the user-facing portal is permitted to reach. An unintended alternate access path allows requests to bypass the controls that should keep unauthenticated users out of sensitive functionality.

Attack vector: An unauthenticated attacker sends a crafted request to the public-facing portal. The appliance processes it without checking whether the sender has any credentials, giving the attacker access to sensitive internal functions. When chained with CVE-2026-83549 (a separate authenticated OS command injection flaw in the admin console), the result is full remote code execution on a device sitting directly on the internet.

Detection strategies: Check for unexpected or repeated requests to internal portal endpoints from external IPs. Review admin console access logs for activity from unrecognised accounts. Look for anomalous outbound connections from the appliance itself.

Recommended actions:

1. Upgrade immediately to firmware 12.4.3-03526 or 12.5.0-02952.
2. If indicators of compromise are found, re-image hardware appliances or re-deploy virtual ones.
3. Reset all user and administrator passwords and TOTP tokens after patching.

What Ruby on Rails is: A popular open-source web application framework used by developers to build websites and web services — including many you use every day without knowing it.

What it is: A critical flaw dubbed KindaRails2Shell allows an attacker to read arbitrary files on the server, steal credentials, and then execute their own code remotely. RCE (remote code execution — when an attacker runs commands on a machine they do not own) is the worst outcome a web vulnerability can produce.

Who's at risk: Any Rails application that uses libvips (an image processing library) for Active Storage and accepts image uploads from untrusted users. VulnCheck identified roughly 7,000 exposed instances in early August, before exploitation began.

CVSS: 9.5 (Critical — patch today.)

Root cause: Rails trusts the content type declared by the client to determine whether a file is an image. libvips ignores that declaration and inspects the file's internal bytes instead. An attacker exploits this disagreement by crafting a file that claims to be a MATLAB image, which tricks libvips into handing it to a chain of libraries that ultimately reads an attacker-chosen file from the server and returns its contents.

Attack vector: An unauthenticated attacker uploads a specially crafted file to any vulnerable image upload endpoint. The server processes it as an image, reads a sensitive file — such as the credentials database — and returns its contents to the attacker. Armed with those secrets, the attacker can forge user sessions and execute code. Critically, VulnCheck found that patching to 8.1.3.1 blocks the file-read path but does not neutralise a separate deserialization gadget, meaning RCE remains possible on patched servers given a valid signature.

Detection strategies: Check server logs for image upload requests containing MATLAB or HDF5 file signatures. Look for unexpected outbound connections from your Rails process. Rails has published forensic tools specifically to detect exploitation attempts — run them.

Recommended actions:

1. Patch to the latest Rails release immediately and apply all available security updates.
2. Restrict image upload endpoints to authenticated users where possible.
3. Run Rails' published forensic detection tools and review logs for signs of prior exploitation.

What PaperCut is: PaperCut NG and MF are print management platforms used by universities, corporations, and governments to control and monitor printing across Canon, Epson, Xerox, Brother, and other devices.

What it is: An actively exploited flaw in PaperCut's web-facing management interface. Attackers can reach it without authentication and gain control of the print server. A second related flaw, CVE-2026-81578, was disclosed alongside it.

Who's at risk: Any organisation running PaperCut NG or MF with the server's web interface reachable from the internet. Universities and government bodies are at particular risk — they have historically been the primary targets of PaperCut exploits.

CVSS: 8.8+ (High — patch this week, sooner if your server faces the public internet)

Root cause: The vulnerability exists in PaperCut's web management interface, which can be reached by unauthenticated external requests. An initial patch was insufficient; PaperCut worked with researchers from Huntress and watchTwr to produce a corrected fix released the following day.

Attack vector: An attacker sends a crafted request to the exposed PaperCut web interface without needing a username or password. From there, they can take administrative control of the print server — which sits inside the corporate network and holds stored print jobs, credentials, and configuration data. Past PaperCut compromises have served as the initial foothold for ransomware deployments.

Recommended actions:

1. Apply the corrected patch released Friday immediately — the first patch was insufficient
2. Remove PaperCut servers from the public internet and restrict web access to trusted IP addresses only
3. Check for evidence of exploitation: review server logs for unexpected authentication events or admin account changes

What Zimbra Collaboration Suite is: A widely used platform that combines email, calendar, contacts, and file sharing — common in government agencies, universities, and mid-to-large businesses.

What it is: A critical remote code execution (RCE — where an attacker can run their own commands on your server without physical access) flaw triggered through Zimbra's SNMP notification processing. SNMP (Simple Network Management Protocol) is a standard used to monitor and manage networked devices. The vulnerability requires no login credentials to exploit.

Who's at risk: Any organisation running Zimbra Collaboration Suite with SNMP notifications enabled — which is the default configuration in affected versions. Federal agencies were given until 24 August to patch or stop using the product.

CVSS: Not confirmed in the source — treat as Critical based on CISA's three-day remediation deadline and confirmed active exploitation.

Root cause: Zimbra fails to properly sanitise (clean and validate) untrusted input received during SNMP notification processing. Think of it like a form that accepts any text without checking whether it contains commands — an attacker can slip instructions through the front door disguised as ordinary data.

Attack vector: An unauthenticated attacker sends a specially crafted SMTP request to a vulnerable Zimbra server. Because the input is not sanitised before being processed, the server executes the attacker's embedded commands with Zimbra-level system privileges. No account, credentials, or social engineering required — just a network path to the server.

Recommended actions:

1. Upgrade to Zimbra Collaboration Suite v10.1.20 immediately — this is the patched release.
2. If patching is not immediately possible, disable SNMP notifications as a temporary mitigation.
3. Treat any previously exposed server as a potential incident: review logs for anomalous SMTP traffic and check for signs of persistence installed before the patch.

What Spring for GraphQL is: Part of Broadcom's Spring application framework, a widely used open-source toolkit for building Java-based enterprise software — Spring for GraphQL specifically handles APIs built using the GraphQL query language.

What it is: Cybersecurity firm Sonatype has flagged CVE-2026-59285 as a critical remote code execution (RCE) flaw — meaning an attacker who successfully exploits it can run their own commands on the affected server, with no need for physical access.

Who's at risk: Developers and organisations running applications built on Spring for GraphQL. Sonatype's analysis found the broader Spring patch batch affects more than 200,000 software components.

CVSS: Not confirmed in the source — treat as Critical until the official advisory publishes a score. Patch today.

Root cause: The source does not detail the precise technical mechanism for CVE-2026-59285. The broader Spring release patched 91 flaws, and Broadcom has attributed the surge in part to increased AI-assisted development introducing new code paths that weren't adequately reviewed.

Attack vector: An attacker targeting a vulnerable Spring for GraphQL endpoint could craft a malicious GraphQL query that triggers unsafe code execution on the server. The exact payload format has not been publicly detailed, which limits immediate exploitation — but that window closes quickly once researchers publish proof-of-concept code.

Detection strategies:

1. Check application logs for unexpected GraphQL queries with unusual structure or parameters.
2. Monitor for new outbound connections from your application server shortly after API calls.
3. Review dependency manifests for Spring for GraphQL and compare against the versions listed in Broadcom's advisory.

Recommended actions:

1. Apply Broadcom's Spring framework updates immediately — this is a critical-severity flaw.
2. Restrict external access to GraphQL endpoints where not required.
3. Enable logging on all GraphQL API calls and alert on anomalous patterns.

No notable new vulnerability disclosed in the last 48 hours. The Vulnerability Watch article provided contained no CVE — it was a general opinion piece on application security practices rather than a disclosure.

What Microsoft Entra ID is: Microsoft Entra ID is a cloud-based identity and access management service — the system that verifies who you are and controls what you can access across Microsoft 365 and connected apps.

What it is: A deserialization flaw (where an application converts user-supplied data back into executable code without properly checking it first) allows an unauthenticated attacker to run arbitrary code on Microsoft's servers over a network connection.

Who's at risk: Any organisation using Microsoft Entra ID was theoretically exposed. Microsoft has confirmed active exploitation in the wild, though no customer action is needed.

CVSS: 10.0 (Critical — the highest possible score). Patch today — though in this case, Microsoft has already applied the fix on their end.

Root cause: The service failed to validate untrusted data before converting it back into active objects. Think of it like a mail room that opens every package and assembles whatever is inside without checking whether the contents are safe.

Attack vector: An unauthenticated attacker sends a specially crafted network request to the Entra ID service. The service deserializes the payload without validation, triggering code execution on Microsoft's infrastructure. No credentials or user interaction were required.

Detection strategies: Microsoft handled the mitigation server-side, so traditional patch detection won't apply. Review your Entra ID sign-in logs for unexpected authentication events around and before the disclosure date. Look for unfamiliar service principals or newly granted admin permissions.

Recommended actions:

1. Confirm your Microsoft 365 tenant is receiving service updates — no manual patch is required, but verify your environment reflects the current service version.
2. Audit recent Entra ID activity logs for anomalous sign-ins or privilege changes.
3. Enable Conditional Access policies and alert on unusual admin role assignments.

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

What JetBrains TeamCity is: A continuous integration and delivery (CI/CD) server — software development teams use it to automatically build, test, and deploy their code.

What it is: CISA has flagged this vulnerability as actively exploited in the wild, per the advisory on The Hacker News. The flaw involves deserialization of untrusted data (a process where software converts incoming data back into executable objects — dangerous when the incoming data is not verified) arriving over the agent polling protocol, the channel build agents use to check in with the server.

Who's at risk: Any organisation running an on-premise TeamCity server that is reachable over a network.

CVSS: 9.8 — Critical. Patch today. Stop reading and go patch.

Root cause: The server processes incoming serialized data (packaged data sent across a network connection) from the agent polling channel without confirming whether the sender is actually a legitimate, authenticated build agent. When software trusts the shape of data rather than its verified origin, an attacker can craft a malicious payload and submit it as though it came from a trusted source.

Attack vector: An unauthenticated attacker who can reach the TeamCity server's network port sends a specially crafted serialized payload over the agent polling protocol. The server deserializes it without authentication checks, executing arbitrary operating system commands at whatever privilege level the TeamCity process runs under. No account credentials are required. A successful hit can expose stored credentials, tamper with build configurations, and compromise software pipelines that push code into production environments.

Detection strategies:

1. Look for unexpected process executions spawned by the TeamCity server process in your endpoint logs.
2. Monitor agent polling protocol traffic for connections from IP addresses outside your known build agent pool.
3. Review TeamCity audit logs for configuration changes or credential access that does not correspond to a known user session.

Recommended actions:

1. Apply the patched TeamCity release immediately — FCEB federal agencies must do so by August 8, 2026.
2. Restrict network access to the TeamCity server so only authorised build agents and administrators can reach it.
3. Review and rotate any credentials stored within TeamCity as a precaution.

What cPanel & WHM is: cPanel is the control panel software that web hosting companies use to let customers manage websites, email accounts, and databases through a browser interface. WHM (Web Host Manager) sits above it, used by hosting administrators to manage the server itself.

What it is: An authenticated cPanel user can cross the privilege boundary between their own account and the server's administrative database identity, executing arbitrary SQL (Structured Query Language — the language used to read and modify databases) with full root-level database permissions. cPanel's own advisory notes this may extend to operating-system-level compromise depending on server configuration.

Who's at risk: Any server running an unpatched version of cPanel & WHM or WP Squared where users have access to the MySQL/MariaDB database feature. Shared hosting environments — where many customers share one server — carry the highest exposure.

CVSS: 9.4 (Critical — patch today.)

Root cause: The flaw lives in cPanel's database-renaming process. When a database is renamed, the system creates a replacement, moves data, recreates permissions, and removes the old database. SQL mode is not preserved during this process, causing subsequent SQL to execute in the database's root administrative context rather than the user's restricted one. The HackerOne CNA classifies this as CWE-89 (SQL injection), though cPanel's own advisory frames it as privilege escalation — two valid descriptions of the same underlying failure.

Attack vector: An attacker with a valid cPanel account triggers the database-rename workflow. Because SQL mode drops to root context mid-operation, commands they supply run with full administrative database privileges. From there, depending on configuration, the path to operating-system access may be short.

Detection strategies: Review database audit logs for unexpected SUPER-privilege operations or schema changes from non-administrative cPanel accounts. Look for database rename events followed immediately by unusual stored procedure creation or user grants. Monitor for unexpected OS-level activity from the database process user.

Recommended actions:

1. Update to a patched build: 11.110.0.137, 11.118.0.71, 11.126.0.78, 11.134.0.48, 11.136.0.32, or 138.1.6 for WP Squared.
2. If immediate patching is not possible, revoke the MySQL/MariaDB feature from cPanel user accounts in WHM as a temporary mitigation.
3. Audit which cPanel accounts currently have database access and restrict to those with a genuine need.

What N-able N-central is: N-central is a remote monitoring and management (RMM) platform used by managed service providers (MSPs) — companies that handle IT infrastructure for other businesses — to monitor, patch, and remotely access their clients' servers and devices.

What it is: This is an authentication bypass (a flaw that lets an attacker skip the login process entirely) that allows an unauthenticated user to take over admin accounts. Both on-premises and cloud-hosted versions are affected.

Who's at risk: MSPs and IT service providers running N-central below version 2026.3.1.7. Because MSPs manage systems for many clients, one compromised N-central console can expose every organisation that MSP supports.

CVSS: Not yet scored — treat as Critical until confirmed. Active exploitation is confirmed in the wild.

Root cause: This is a bypass of a previously patched flaw (CVE-2026-18556). Attackers found a new path around the fix and began exploiting it in late July 2026. The authentication layer failed to close all routes into privileged account access.

Attack vector: An attacker with network access sends a crafted request to the N-central console, bypasses authentication, and gains full admin control. From there, they can deploy scripts to managed endpoints, run remote sessions on critical servers, and register Cloudflare tunnels (persistent encrypted channels that survive even after server access is revoked) to maintain a foothold.

Detection strategies: Check N-central audit logs for admin account creation or logins from unrecognised IP addresses. Look for new Cloudflare tunnel registrations or unfamiliar services appearing on managed endpoints. Monitor for unexpected script deployments pushed through the N-central agent.

Recommended actions:

1. Upgrade to N-central version 2026.3.1.7 immediately.
2. Review indicators of compromise published by N-able and Huntress.
3. Audit admin accounts and active Cloudflare tunnels across your N-central environment.

CVE ID confirmed in source — verify details against the official SonicWall advisory before acting.

What SonicWall SMA1000 is: A hardware appliance organisations use to give remote workers secure access to internal corporate networks, sitting at the edge of the network as a gateway.

What it is: CVE-2026-15409 allows an unauthenticated attacker (someone with no account or credentials) to open a WebSocket tunnel (a persistent two-way connection channel) directly to restricted internal services. A second flaw, CVE-2026-15410 (CVSS 7.2), can then be used to escalate privileges to root, giving the attacker full control of the appliance. Ransomware group INC has been observed chaining both flaws together.

Who's at risk: Any organisation running SMA1000 appliances that have not applied the July 14 patch. Exploitation has been confirmed in the wild since at least June 22.

CVSS: 10.0 — Critical. Patch today. This is the highest possible score.

Root cause: The appliance failed to enforce authentication before allowing WebSocket connections to restricted service endpoints. Think of it like a secure building where the front desk waves anyone through without checking ID, because the system assumed only staff would know to walk up to that door.

Attack vector: An attacker sends an unauthenticated WebSocket request to the exposed endpoint. The appliance accepts the connection. From there, CVE-2026-15410 is used to elevate access to root. With root access, attackers have deployed backdoors and harvested credentials, and in some cases pivoted into internal corporate networks from the compromised appliance.

Detection strategies: Look for unexpected WebSocket connections to internal service ports originating from external IP addresses. Review SMA1000 authentication logs for access events with no corresponding valid session. Monitor for new or unrecognised files written to the appliance filesystem after June 22.

Recommended actions:

1. Apply the SonicWall patch released July 14, 2026, immediately.
2. Audit appliance logs for signs of compromise dating back to June 22.
3. Isolate any unpatched SMA1000 devices from internal networks until patching is complete.

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

What Coldcard is: Coldcard is a Bitcoin-only hardware wallet — a physical device that stores your private keys offline, made by Canadian company Coinkite.

What the flaw is: A 2021 firmware integration error caused wallet seed generation to use a weak software PRNG instead of the device's dedicated hardware RNG (random number generator). The software fallback produced seeds with far less entropy (unpredictability) than a secure wallet requires — roughly 40 bits on the Mk3, versus the 128 bits a standard 12-word seed should provide.

Who is at risk: Anyone whose seed was generated on an affected firmware version. Coinkite's advisory lists Mk3 versions 4.0.1 through 4.1.9 as vulnerable; Block's independent research also places Mk2 and Mk3 versions from 4.0.0 onward on the vulnerable path. Mk4 and Mk5 devices running firmware before 5.6.0, Q devices before 1.5.0Q, and Edge builds before 6.6.0X (Mk4/Mk5) or 6.6.0QX (Q) are also affected. The version running today is irrelevant — what matters is the version running when the seed was first created.

Recommended actions:

1. Install the emergency firmware released July 31 for your model.
2. If your seed was generated on an affected version, generate a brand-new seed on patched firmware and transfer all funds to the new wallet immediately.
3. Do not restore your old seed to any device or wallet — the weakness is in the seed itself, not the device.

What Adobe Campaign Classic is: Adobe Campaign Classic is enterprise marketing software used by large organisations to manage and automate mass email, SMS, and direct mail campaigns.

What it is: A flaw in how the software checks whether a user has permission to perform certain actions allows an attacker to run arbitrary code (any program the attacker chooses) on the affected server, with no interaction required from a legitimate user. The flaw carries a CVSS (Common Vulnerability Scoring System — a standardised 0–10 scale for severity) score of 10.0: Critical. Patch today.

Who's at risk: Organisations running Adobe Campaign Classic prior to version 7.4.3 build 9398 on Windows or Linux. Exposure is highest for internet-facing installations.

CVSS: 10.0 (Critical) — Patch today.

Root cause: The software fails to correctly verify whether a requesting party is authorised before executing privileged operations. When authorisation checks are absent or bypassed, the server treats an attacker's request with the same trust as a legitimate administrator's. Adobe has not disclosed the precise technical mechanism publicly.

Attack vector: An attacker sends a crafted request to an affected Campaign Classic server without needing a valid account or any victim to click anything. The server, lacking proper authorisation checks, processes the request and executes attacker-supplied code under the permissions of whatever account the server runs as.

Detection strategies: Review server-side logs for unexpected process spawning from the Campaign Classic service account. Look for outbound connections to unfamiliar hosts originating from the application process. Flag any authentication or permission-related errors that appear in bulk or in unusual sequences.

Recommended actions:

1. Upgrade Adobe Campaign Classic to v7.4.3 build 9398 on all Windows and Linux deployments immediately.
2. Restrict network access to Campaign Classic servers to known, trusted IP ranges.
3. Monitor application logs for anomalous process execution or unexpected outbound traffic.

What Chrome is: Google Chrome is the world's most widely used web browser, installed on billions of devices for everyday browsing, work, and personal use.

What it is: Google's AI security tooling discovered a flaw hiding in Chrome's code for 13 years, disclosed in full this week via Security Week. The vulnerability is an insufficient data validation error in Chrome's Navigation component that allows a sandbox escape (a breakout from the restricted zone where untrusted web content is supposed to run, isolated from your actual files and system).

Who's at risk: Anyone running Chrome below version 145, on any operating system.

CVSS: 9.8 — Critical. Patch this week.

Root cause: Chrome runs web content inside a sandboxed renderer process, a walled-off environment designed to keep untrusted code away from your system. The Navigation component failed to properly validate data passed between that renderer and the browser's core process. This meant a compromised renderer could trick the browser into reading local files it should never be able to access.

Attack vector: An attacker crafts a malicious HTML page and lures the target into visiting it. The page exploits the validation gap in the Navigation component, escaping the sandbox and gaining access to local files on the device.

Recommended actions:

1. Open Chrome, go to Settings → Help → About Google Chrome, and confirm you are on version 145 or later.
2. Enable automatic updates if they are not already on.
3. If you manage a fleet of devices, prioritise this update across all Chrome installations this week.

CVE ID confirmed in source — read the full advisory here.

What Ruby on Rails is: Ruby on Rails is a popular open-source web development framework used to build web applications. Active Storage is its built-in system for handling file uploads.

What the flaw is: A critical vulnerability in Active Storage allows an unauthenticated attacker to read files directly from the web server by uploading a crafted image. Those files can include secrets that unlock deeper access to the entire application.

Who's at risk: Any web application built on the affected Rails versions that accepts image uploads from the public and uses libvips (an image-processing library) for processing. Applications using MiniMagick (an alternative image-processing library) are not exposed through this path.

CVSS: 9.5 — Critical. Patch today.

Root cause: libvips supports certain file-loading operations that its own maintainers flag as unsafe for hostile input. Active Storage did not restrict access to these operations. It passed untrusted uploaded files directly into them. No special upload endpoint was needed — even standard variant generation triggered the vulnerable path.

Attack vector: An attacker uploads a specially crafted file (reportedly a MATLAB/HDF5 format file) through any public upload form. libvips processes it and reads internal server files. The attacker recovers SECRET_KEY_BASE (a master signing key Rails uses to verify session data). With that key, an attacker can forge authenticated session tokens, enabling RCE (remote code execution — running arbitrary commands on the server) or lateral movement (moving from one compromised system into others connected to it).

Detection strategies:

• Unexpected or malformed file types appearing in upload logs (MATLAB, HDF5, or similar scientific formats submitted to image upload endpoints)
• Anomalous outbound network requests from your Rails worker processes, particularly curl-style callbacks to external addresses
• Unrecognised session tokens appearing in application logs after no corresponding login event

Recommended actions:

1. Upgrade Rails to 7.2.3.2, 8.0.5.1, or 8.1.3.1 immediately. Rails 7.1 and earlier are end-of-life and will not receive a backport.
2. If you cannot patch immediately and run libvips 8.13 or later, set the environment variable VIPS_BLOCK_UNTRUSTED=1 or call Vips.block_untrusted(true) via ruby-vips 2.2.1 or later.
3. Rotate all secrets readable by the application process: secret_key_base, master key, database credentials, cloud storage keys, and third-party API tokens.

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

What OpenWrt is: OpenWrt is an open-source operating system that replaces the factory firmware on home and small-business routers, giving users more control over their network hardware.

What it is: A stack overflow (a flaw where a program writes more data into a fixed memory area than it was designed to hold, overwriting adjacent memory) in the DHCPv6 request handler inside a component called odhcpd. An unauthenticated attacker on the network can trigger it with a single crafted network packet.

Who's at risk: Anyone running OpenWrt versions before 24.10.8 or 25.12.5 with DHCPv6 enabled — the default configuration on most deployments.

CVSS: 9.8 — Critical. Patch today.

Root cause: The odhcpd component processes incoming DHCPv6 requests into a fixed 512-byte stack buffer without adequately checking whether the incoming data fits before appending reply information. Because odhcpd runs as root, and because most embedded routers lack stack canaries (small memory guards that detect overflow attempts) or ASLR (address space layout randomisation, which randomises memory locations to hinder exploit code), an overflow reliably translates into remote code execution rather than just a crash.

Attack vector: An attacker sends a crafted DHCPv6 REQUEST to UDP port 547. No authentication is required. The malformed packet overflows the stack buffer inside odhcpd, allowing the attacker to redirect execution and run arbitrary commands as root. Public proof-of-concept code is available in the advisory.

Detection strategies: Check odhcpd logs for malformed or unexpected DHCPv6 REQUEST messages on port 547. Look for unexpected root-level processes spawned by odhcpd. Monitor for unusual outbound connections from your router immediately after DHCPv6 activity.

Recommended actions:

1. Update to OpenWrt 24.10.8 or 25.12.5 using the OpenWrt Firmware Selector.
2. If you cannot patch immediately, consider disabling DHCPv6 on interfaces not actively using IPv6.
3. Begin planning migration to the 25.12 series before the 24.10 branch reaches end of life in September 2026.

What TeamCity is: TeamCity is a continuous integration and delivery server made by JetBrains — software used by development teams to automatically build, test, and deploy code.

What it is: A critical authentication bypass that allows an unauthenticated attacker to reach internal server functionality and execute operating system commands — all without ever logging in.

Who's at risk: Any organisation running TeamCity On-Premises with an internet-facing or network-accessible server. TeamCity Cloud instances are already patched.

CVSS: 9.8 — Critical. Patch today.

Root cause: The flaw sits in the agent polling protocol, a communication channel normally used by build agents (automated workers) to check in with the TeamCity server. The server failed to properly enforce authentication checks on this channel, meaning an attacker can send requests through it as if they were a legitimate agent and reach privileged functionality they should never be able to access. Think of it like a staff entrance with a broken lock — the front desk checks every visitor, but this side door waves anyone through.

Attack vector: An attacker with HTTP or HTTPS access to the TeamCity server sends crafted requests through the agent polling endpoint, bypassing authentication entirely. Once past that check, they can issue operating system commands that run with the same permissions as the TeamCity server process itself — which in many deployments means access to stored credentials, build configurations, source code, and deployment pipelines. No user interaction and no existing account is required.

Detection strategies:

1. Review TeamCity server logs for unexpected or unauthenticated requests to agent polling endpoints, particularly from unfamiliar IP addresses.
2. Check for unexpected outbound connections from the TeamCity host, especially to unusual destinations.
3. Audit recently modified build configurations, stored credentials, or administrator accounts for changes you did not make.

Recommended actions:

1. Upgrade to TeamCity On-Premises version 2025.11.7 or 2026.1.3 immediately.
2. If upgrading now is not possible, install JetBrains' security patch plugin (available for versions 2017.1 and above) as an interim measure.
3. Place the TeamCity server behind a VPN or restrict network access so it is not reachable from the public internet.