Cisco Patches Critical SD-WAN, IOS XE, FMC Vulnerabilities

Cisco on Wednesday rolled out patches for two dozen vulnerabilities across its products, including critical-severity bugs in Catalyst SD-WAN, IOS XE, and Secure Firewall Management Center (FMC).

For Catalyst SD-WAN, the company released five fixes, noting that the CVEs were assigned to multiple weaknesses grouped by the underlying vulnerability class.

Three of the CVEs, namely CVE-2026-20303, CVE-2026-20304, and CVE-2026-20310, have a CVSS score of 9.9 and are described as improper input validation, improper access control, and improper link resolution before file access.

The remaining two, CVE-2026-20312 and CVE-2026-20313, are high-severity flaws described as cleartext storage of sensitive information and improper validation of specified quantity in input.

IOS XE received seven fixes, and the assigned CVEs group multiple issues by their underlying vulnerability class.

Two of them, CVE-2026-20272 (CVSS score of 9.8) and CVE-2026-20267 (CVSS score of 9.0), are critical-severity command injection and improper access control defects, while the rest are high-severity flaws.

Advertisement. Scroll to continue reading.

FMC received patches for CVE-2026-20079 (CVSS score of 10), a critical authentication bypass that allows remote, unauthenticated attackers to execute scripts and gain root privileges.

“An attacker could exploit this vulnerability by sending crafted HTTP requests to an affected device. A successful exploit could allow the attacker to execute a variety of scripts and commands that allow root access to the device,” Cisco notes.

The company also patched high-severity security defects in Integrated Management Controller (IMC), IOS XE, and IOS, and medium-severity bugs in IOS XE, Terminal Service (TS) Agent, Catalyst SD-WAN Manager, RoomOS, and IMC.

Of these, CVE-2026-20200 (CVSS score of 8.8) deserves special attention. It is a high-severity improper validation of user-supplied input issue in IMC that could be exploited remotely to execute arbitrary commands and gain root privileges.

While the flaw’s exploitation requires authentication, proof-of-concept (PoC) code targeting it exists, Cisco warns. The weakness affects UCS C-Series M7 and M8 Rack Servers in standalone mode.

Cisco says it is not aware of any of these vulnerabilities being exploited in the wild. Additional information can be found on the company’s security advisories page.

https://www.securityweek.com/cisco-patches-critical-sd-wan-ios-xe-fmc-vulnerabilities/

Hackers Start Exploiting Recent JetBrains TeamCity Vulnerability

Threat actors have started exploiting a recently patched vulnerability in JetBrains TeamCity, the US cybersecurity agency CISA warns.

A continuous integration and continuous delivery (CI/CD) platform, TeamCity provides automated software building and deployment and is a central component of enterprise workflows, collaboration, and development practices.

Tracked as CVE-2026-63077 (CVSS score of 9.8), the critical security defect is related to deserialization of untrusted data and allows unauthenticated attackers to achieve remote code execution (RCE) via HTTP/S requests.

Impacting all TeamCity On-Premises versions, the flaw enables attackers to “bypass authentication checks and execute arbitrary operating system commands with the privileges of the TeamCity server process,” JetBrains warned last week.

Patches for the issue were included in TeamCity versions 2025.11.7 and 2026.1.3. A security patch plugin for version 2017.1+ was also released.

“An unauthenticated attacker could exploit the vulnerability via the TeamCity agent polling protocol,” JetBrains said, urging organizations to apply the patches to their TeamCity On-Premises deployments as soon as possible.

Advertisement. Scroll to continue reading.

In its advisory, JetBrains noted that the security defect was reported privately and that it was not aware of any active exploitation.

On Wednesday, roughly a week after public disclosure, CISA added CVE-2026-63077 to its Known Exploited Vulnerabilities (KEV) catalog, urging federal agencies to patch it within three days, as mandated by BOD 26-04.

There does not appear to be any public information on the attacks exploiting the vulnerability.

https://www.securityweek.com/hackers-start-exploiting-recent-jetbrains-teamcity-vulnerability/

How a $50,000 Exploit Chain Turned Bixby Against Samsung Phones

BLACK HAT – Two security researchers found a way to exploit vulnerabilities in Samsung software, including the virtual assistant Bixby, to hack mobile devices.

The research was conducted by Dimitrios Valsamaras, senior security researcher at Microsoft, and Ken Gannon, head of mobile research at Mobile Hacking Lab.

Gannon and Valsamaras demonstrated the vulnerabilities at the Pwn2Own Ireland hacking competition in October 2025, where they earned $50,000 after exploiting them to hack a Samsung Galaxy S25 device.

The researchers have now detailed their findings in a talk at the Black Hat conference, describing the vulnerabilities they discovered and how they were chained to achieve remote system-level compromise.

The exploit developed by Gannon and Valsamaras starts with an attacker tricking the targeted user into clicking a link delivered via malicious ads or a messaging application.

After the victim clicks on the link, a vulnerability tracked as CVE-2025-21079 is exploited to force Samsung Members to connect to a malicious website. Samsung Members is an official user community, diagnostics, and support app that is preloaded on many mid-range and flagship Galaxy smartphones.

Advertisement. Scroll to continue reading.

The malicious site then forces Samsung Members to open the Samsung Account app, which is designed to connect users to Samsung services.

Next, a different vulnerability, CVE-2025-58486, is used to force Samsung Account to connect to an attacker-controlled website. This site then exploits an XSS vulnerability tracked as CVE-2025-58487 to force Samsung Account to open Bixby, the virtual assistant that can handle voice commands, visual searches, and device automation routines.

The researchers told SecurityWeek that this is possible because the Samsung Account app has a special permission that is required to interact with a specific ‘entry point’ in Bixby.

“Think of it as a ‘side entrance’ and Samsung Account happens to be a key holder for the ‘side entrance,’” explained Gannon.

The next stage of the attack involves a Capsule, a hidden background service inside an app that acts like a mini internal server. When users issue a voice command, Bixby translates the request and sends it to the app’s Capsule to perform the actual task. Because Capsules can directly control app functions, Samsung restricts access so that normally only Bixby is allowed to talk to them.

However, the researchers reverse-engineered the Capsule infrastructure on Samsung phones and found a way to force Bixby to use various Capsules maliciously.

This enabled an attacker to exfiltrate sensitive data and achieve system-level permissions on the Android device—the highest privilege level that can be achieved on a stock consumer device.

The researchers showed that once an attacker has obtained ‘system’ permissions, they can achieve remote code execution and take control of the device.

The researchers said they successfully reproduced the exploit on Samsung Galaxy S25, S24, and Flip 7 smartphones.

Vulnerabilities patched by Samsung

Samsung started patching the vulnerabilities a few weeks after the Pwn2Own competition. Specifically, the company rolled out patches for the Samsung Members application in November 2025, preventing the exploit chain from being triggered via a web browser or messaging app. Patches released in December fixed the Samsung Account flaws.

The researchers told SecurityWeek that the attack works on older Samsung devices, which may not have received the patches, but noted that the exploit requires all of the targeted apps to be installed. While flagship models come with the apps preinstalled, it’s unclear if that applies to budget models as well.

Samsung has not responded to SecurityWeek’s request for comment.

https://www.securityweek.com/how-a-50000-exploit-chain-turned-bixby-against-samsung-phones/

New Attack Methods Enable Malware to Hijack Passkey-Protected Accounts

Palo Alto Networks researchers have disclosed the details of new attack methods targeting passwordless authentication, showing how malware can hijack a passkey-protected account.

Passkeys are increasingly adopted by tech giants and are widely recommended because they are more secure against phishing.

The new attack methods, named ‘Pass-ta-key’ by Palo Alto Networks, focus on Google-synced passkeys. The security firm’s researchers showed how a threat actor could use the techniques to take over accounts without needing privilege escalation or user interaction.

In a Pass-ta-key attack, malware already present on a Windows machine running Chrome can examine the browser’s local synchronization database to identify which online accounts the user has protected with passkeys, along with associated usernames and encrypted credential material.

The malware recovers a device identity key that Chrome stores on disk or in memory. It then uses Windows cryptographic APIs to generate a signature over a challenge received from Google’s cloud authenticator service, without any biometric prompt, device unlock, or elevated privileges.

The cloud service treats the signed request as coming from a legitimate trusted device. It returns a valid authentication assertion, which the attacker forwards to the target website to complete the login.

Advertisement. Scroll to continue reading.

In a more advanced variant, dubbed ‘Silver Pass-ta-key’, the malware forces Chrome into a device re-registration process. During a short window in that process, it registers its own user-verification key with the cloud authenticator. Once registered, the attacker can later authenticate from a completely different machine.

The most severe technique, ‘Golden Pass-ta-key’, extracts a master secret that briefly appears in Chrome’s process memory during re-enrollment. Possession of this secret allows the malware to decrypt every synchronized passkey private key belonging to the account, enabling the attacker to decrypt future passkeys as well.

Google has been notified and Palo Alto Networks’ blog post indicates that it has rolled out some mitigations.

https://www.securityweek.com/new-attack-methods-enable-malware-to-hijack-passkey-protected-accounts/

Ruby on Rails Patches Critical Vulnerability

Ruby on Rails this week rolled out patches for a critical vulnerability that could allow unauthenticated attackers to achieve remote code execution (RCE).

A server-side web application framework written in Ruby, Ruby on Rails is used for the fast building of full-stack web applications and APIs.

Tracked as CVE-2026-66066 (CVSS score of 9.5), the critical security defect is described as an arbitrary file read that potentially exposes secrets, allowing remote attackers to execute code or move laterally to other systems.

“In its default configuration, a Rails application that displays image variants may allow an unauthenticated attacker to read arbitrary files from the server, including the process environment,” Ruby on Rails’ maintainers note in an advisory.

Within the exposed environment, the advisory explains, attackers could find secret_key_base and credentials for external systems, which can be abused to escalate the attack to RCE.

The issue impacts applications that use the libvips library for Active Storage image processing and that allow image uploads from untrusted users.

Advertisement. Scroll to continue reading.

Because libvips marks some file read and write operations as ‘unfuzzed’ (unsafe for untrusted content) and Active Storage did not disable the unfuzzed operations, an attacker could upload a crafted file to invoke one of these operations.

“We are aware of a mechanism by which an attacker, by uploading a crafted file, is able to cause disclosure of the contents of arbitrary files accessible on the filesystem of the targeted application,” Ruby on Rails’ advisory reads.

CVE-2026-66066 was patched in Active Storage versions 7.2.3.2, 8.0.5.1, and 8.1.3.1. Users are advised to update their deployments as soon as possible, as well as to update libvips to at least version 8.13, as previous library releases do not support disabling unfuzzed operations.

“Upgrading closes the vulnerability but does not undo an exfiltrated secret if that already occurred. An affected application should treat every secret readable by the application process as potentially exposed and change it,” Ruby on Rails notes.

According to cybersecurity firm Rapid7, as of July 30, there is no evidence that the security defect has been exploited in the wild.

https://www.securityweek.com/ruby-on-rails-patches-critical-vulnerability/

Google AI Uncovers 13-Year-Old Chrome Flaw Amid Record Patching Pace

Google this week confirmed that this year’s surge in Chrome vulnerabilities has been driven by the use of AI.

The increase in Chrome bugs started in April and has continued throughout July, with the latest browser release containing 370 security fixes and bringing the total number of bugs patched this year to over 1,800.

Google patched 1,072 security defects with the Chrome 149 and 150 releases, “surpassing the total number of security bugs fixed across the prior 23 milestones combined.”

This was the result of using an agent harness that leverages Gemini to identify security flaws across Chrome’s codebase with increased efficiency, the internet giant says.

What validated the AI-powered vulnerability detection, Google says, was the discovery of a sandbox escape that lurked in the browser for 13 years.

Tracked as CVE-2026-3545 (CVSS score of 9.8) and patched in early May in Chrome 145, the issue could have allowed “a compromised renderer to trick the browser into reading local files,” it says.

Advertisement. Scroll to continue reading.

Described as an insufficient data validation in Navigation, the vulnerability could have been exploited via crafted HTML pages to perform a sandbox escape.

The Chrome Security team started using LLMs in 2023, but it was the agent harness built in early 2026 that has been essential to finding and patching more flaws in the browser.

It has support for model interoperability, was trained on a knowledge base of previously identified CVEs and of Chrome’s entire Git history, leverages developer-supplied SECURITY.md files that are consumed by a “critic” agent, and can run vulnerability-finding models over the codebase multiple times.

“We’ve built all of this with safety in mind, and have put in place guardrails to mitigate the risk of AI behaving unexpectedly. Our AI analyzes source code strictly at rest, operating on locked-down machines that lack general internet access,” Google explains.

While also relying on AI for bug validation, triaging, and patch generation, the internet giant continues to use other security testing infrastructure for bug detection, and welcomes researchers submitting vulnerability reports through its VRP.

“At this point, we have LLMs generating candidate fixes for most vulnerabilities, dramatically increasing the rate of security fixes in recent Chrome releases,” Google says.

Additionally, the company is relying on AI to prevent new security bugs by identifying and eliminating them “as close to code submit-time as possible” and by neutralizing issues in the tree that could impact code deemed safe in isolation.

Reducing the patch gap and eliminating memory safety bugs

To reduce the patch gap, Google is also piloting a twice-a-week Chrome security release cadence, which will complement the two-week schedule for major Chrome releases that was announced in March.

“We are working on automating the generation of release notes and CVE descriptions from security bug fixes to eliminate manual bottlenecks and shorten the window between vulnerability discovery and public disclosure,” the company says.

Google is also working on ensuring that Chrome is always up to date on users’ machines, through dynamic patching, which eliminates the need to restart the browser when applying updates, seamless session restoration, and restarts while in a windowless state (the application runs in the background while all windows are closed).

Additionally, Google is working on eliminating entire classes of security issues from Chrome, such as memory safety flaws. For that, it is hardening the runtime environment to squash C++ bugs, and is transitioning to memory-safe languages.

In this regard, it is expanding MiraclePtr to more libraries and deploying MiracleObject to the GPU main thread to neutralize use-after-free defects. In addition, it’s taking a ‘spanification’ effort to eliminate out-of-bounds weaknesses, and is integrating memory allocation protections to block integer overflows.

In the long term, Google is transitioning Chrome’s codebase to memory-safe languages like Rust, through building a centralized Rust SDK, deploying Rust to replace most flawed code segments, and writing new modular components in Rust.

“In addition to Rust, we are also exploring options like implementing the browser’s top-level user interface using HTML, CSS, and TypeScript to further reduce dependencies on traditional C++ frameworks,” Google notes.

According to the company, keeping the open source software ecosystem secure is another critical aspect of improving Chrome users’ protections. It has been using automated vulnerability scanning pipelines to keep dependencies patched and will move all Chrome third-party dependencies onto automated update pipelines.

“Every bug found and fixed is one less foothold for an attacker. But discovering and fixing a bug is only half the battle — we must also ship the fix and apply the update for users faster than adversaries can exploit the bug, and invest in projects that mitigate or eliminate classes of bugs through accelerated release cadences, dynamic patching, and opportune restarts, we are driving toward a browser that is continuously protected without disrupting the user,” Google notes.

https://www.securityweek.com/googles-ai-agent-uncovers-13-year-old-chrome-flaw-amid-record-patching-pace/

Critical Flaw Allowed to Azure Cosmos DB Pwnage

A critical vulnerability in the Azure Cosmos DB database service could have allowed attackers to compromise all databases on the service, cybersecurity outfit Wiz reports.

Referred to as CosmosEscape, the security defect could have allowed an attacker to obtain a platform-wide key and retrieve the primary key of any Cosmos DB account, gaining full read and write access across the service.

Armed with the key, an attacker could have listed all databases on the service, filtering them by specific organization identifiers, such as subscription and tenant IDs.

“Chained together, these capabilities could have enabled precision targeting at platform scale: from identifying a specific organization’s databases to compromising them, all from publicly accessible endpoints,” Wiz says.

According to the cybersecurity firm, because Microsoft uses Cosmos DB to store data across Entra ID, Teams, and Copilot, the vulnerability potentially exposed the tech giant’s databases to unauthorized access.

The issue could have been exploited through the Gremlin API, a popular graph query language that relies on a custom Gremlin engine, compiling queries into .NET code that was executed in a sandbox.

Advertisement. Scroll to continue reading.

Pwning the sandbox

While the engine enforced restrictions to prevent access beyond Gremlin operations, it did not account for .NET reflection, which Wiz used to build arbitrary code execution primitives.

“By bypassing the Gremlin sandbox, we’ve gained code execution on the DB Gateway, a service that executes customer queries on their behalf, running on multi-tenant Service Fabric clusters,” Wiz explains.

The cybersecurity firm then discovered that the gateway was using a signing key to retrieve customer accounts’ primary keys and access their databases, and that the signing key worked across tenants, regions, and even APIs.

“It was a platform-wide key that could retrieve the primary key for any Cosmos DB account on the service, all through publicly accessible endpoints. We dubbed it the Cosmos Master Key,” Wiz notes.

Through the master key, the cybersecurity firm’s researchers could access a configuration store containing details on every Cosmos DB account, including names, subscription IDs, tenant IDs, and various other configuration data.

Pwning the databases

“The Config Store was itself a Cosmos DB database, meaning it could be queried with the full flexibility of CosmosDB’s SQL engine. It also meant that the Cosmos Master Key could retrieve its primary key – enabling attackers that exploited CosmosEscape to list all accounts in a region, or query by specific tenant ID to identify a specific organization’s databases,” the company explains.

An attacker with the master key and access to the configuration store could enumerate all Cosmos DB accounts, filter them, and retrieve a target’s primary key to gain full read and write access to all their databases.

According to Wiz, the attack could also be mounted against private and network-isolated Cosmos DB accounts, as well as Microsoft’s own databases.

Wiz reported the vulnerability to Microsoft in November 2025. Within two days, Microsoft deployed a hotfix to block the attack vector. In July, the tech giant completed the rollout of a long-term architectural fix across all regions.

“Microsoft conducted extensive reviews of access logs and found no evidence of unauthorized activity outside of the researcher’s testing activity, and no customer data was accessed. There is no customer action required,” the company said.

https://www.securityweek.com/critical-flaw-led-to-azure-cosmos-db-pwnage/

Critical Code Execution Vulnerability Patched in TeamCity

JetBrains this week rolled out patches for a critical-severity vulnerability in TeamCity On-Premises that can be exploited without authentication.

Tracked as CVE-2026-63077 (CVSS score of 9.8), the security defect can be exploited via HTTP/S to bypass authentication and achieve remote code execution (RCE).

“An unauthenticated attacker could exploit the vulnerability via the TeamCity agent polling protocol to bypass authentication checks and execute arbitrary operating system commands with the privileges of the TeamCity server process,” JetBrains explains in its advisory.

Depending on the available privileges, an attacker could access TeamCity data, configurations, and credentials, could tamper with the server state, and could potentially compromise build artifacts and downstream CI/CD pipelines.

According to JetBrains, the flaw affects all TeamCity On-Premises versions. The company has already rolled out mitigations for TeamCity Cloud instances and has no evidence that the bug has been exploited in the wild.

“A fix for this vulnerability has been introduced in versions 2025.11.7 and 2026.1.3. We have also released a security patch plugin for 2017.1+ so that customers who are unable to upgrade can still patch their environments,” JetBrains announced.

Advertisement. Scroll to continue reading.

Users are advised to download and install either the latest version of TeamCity or the security patch plugin as soon as possible (the plugin resolves only this CVE, the company notes).

JetBrains also recommends limiting access to internet-facing TeamCity servers, running all servers with the minimum required operating system privileges, and using VPN connections or implementing additional protections to prevent unauthorized access.

“TeamCity servers should also run on dedicated hosts separate from build agents,” the company notes.

https://www.securityweek.com/critical-code-execution-vulnerability-patched-in-teamcity/

Critical Ruflo Flaw Lets Attackers Spawn Rogue AI Swarms

Unauthenticated attackers could exploit a critical-severity vulnerability in the open source AI agent orchestration platform Ruflo to execute commands inside the container, Noma Labs security researchers warn.

A popular automation assistant with over 67,000 GitHub stars, Ruflo (formerly Claude Flow) comes with a multi-model AI chat interface, agent swarms, persistent memory, and built-in Model Context Protocol (MCP) tool calling.

Ruflo allows organizations to use AI applications, courtesy of agent swarms (support for coordinating up to 100 agents on shared enterprise-grade tasks), long-term memory enabling agents to recall past interactions, and an integrated MCP server enabling agents to execute various tasks.

“The bridge exposes 233 tools covering shell access, database operations, agent management, and memory storage, making it the single point through which every agent action flows. Because the MCP Bridge requires direct access to the underlying system resources to execute these commands, it creates a high-stakes security boundary,” Noma explains.

Tracked as CVE-2026-59726 (CVSS score of 10/10), the security defect was found in the MCP bridge in ruflo/docker-compose.yml, which exposed the POST /mcp endpoint without authentication.

Because in default docker-compose deployments the bridge and MongoDB were bound to all interfaces, an unauthenticated attacker could invoke terminal_execute to run commands inside the bridge container, Ruflo’s advisory reads.

Advertisement. Scroll to continue reading.

Successful exploitation of the bug could allow the attacker to gain shell access as node, read provider API keys, spawn swarms on the victim’s keys, and inject poison patterns into the AgentDB learning store to tamper with the AI outputs for all users.

According to Noma, which named the bug RufRoot, the root cause is that, in self-hosted deployments, the docker-compose.yml binds port 3001 to 0.0.0.0 by default, exposing all network-reachable instances to exploitation without authentication.

“The MCP Bridge isn’t a random auxiliary debug interface; rather, it is Ruflo’s central nervous system. Every tool call, every agent action, every memory operation goes through the MCP Bridge. Mistakenly giving unauthenticated access to the MCP Bridge means giving unauthenticated access to everything,” Noma explains.

With a single HTTP request targeting ruflo__terminal_execute, an attacker could take over the agent swarm, because the command would run as the container’s node user, providing access to all accessible assets without further escalation.

“Once you have command execution, achieving full compromise is just chaining more requests to the same endpoint,” Noma explains.

An attacker could exploit the vulnerability for reconnaissance, remote code execution (RCE), API key and conversation theft, spawning attacker-controlled agent swarms, poisoning the learning pipeline to produce attacker-influenced output, deploying persistent backdoors, and clearing shell history to remove traces.

The vulnerability was patched in Ruflo version 3.16.3. The fix addresses all attack vectors, and Ruflo’s maintainers published remediation steps for users with exposed instances.

https://www.securityweek.com/critical-ruflo-flaw-lets-attackers-spawn-rogue-ai-swarms/

Apple Patches 87 Vulnerabilities in iOS, 155 in macOS Tahoe

Apple announced on Monday that it has released patches for dozens of vulnerabilities discovered recently in its operating systems.

The company patched 87 vulnerabilities with the release of iOS 26.6 and iPadOS 26.6.

The flaws can be exploited to access sensitive user data, fingerprint users, cause a DoS condition, execute arbitrary code, delete files, modify the file system, bypass security, add contacts without authorization, spoof the UI, and escalate privileges.

In macOS Tahoe 26.6, Apple fixed 155 vulnerabilities, including ones allowing access to sensitive user data, arbitrary code execution, security bypasses, and DoS attacks.

macOS Sequoia 15.7.8 includes fixes for 138 security holes, while macOS Sonoma 14.8.8 resolves 127 issues.

Many of the vulnerabilities were patched across all of these platforms.

Advertisement. Scroll to continue reading.

“The one worth a second look is CVE-2026-43810, where Apple notes a remote user may be able to corrupt kernel memory, because remote changes the economics of an attack chain considerably,” commented Adam Boynton, senior enterprise strategy manager at Jamf.

Roughly 100 flaws have been patched by Apple in each of its other operating systems: watchOS, tvOS, and visionOS.

The latest Safari update fixes nearly a dozen vulnerabilities, including ones that can be exploited to access sensitive user data or crash the browser.

The advisories do not mention in-the-wild exploitation. Additional details are available in Apple’s security advisories.

https://www.securityweek.com/apple-patches-87-vulnerabilities-in-ios-155-in-macos-tahoe/