A recent discussion surfaced on Reddit's NetSec community highlighting techniques for exploiting Microsoft SQL Server (MSSQL) to execute commands more effectively. Although no specific vulnerabilities or affected MSSQL versions are detailed, the content suggests advanced exploitation methods that could be leveraged by attackers to run arbitrary commands on compromised MSSQL instances. No known exploits in the wild have been reported yet, and the discussion level is minimal, indicating early-stage awareness rather than widespread attack activity. The threat is assessed as medium severity due to the potential for command execution on database servers, which could impact confidentiality and integrity if exploited. European organizations using MSSQL, especially those with internet-facing database servers or weak access controls, could be at risk. Mitigation should focus on restricting MSSQL access, enforcing least privilege, monitoring for unusual command execution, and applying best practices for MSSQL security. Countries with significant MSSQL deployments and critical infrastructure relying on Microsoft technologies, such as Germany, the UK, France, and the Netherlands, may be more likely affected. Given the lack of detailed technical data and no known active exploitation, the suggested severity is medium. Defenders should prioritize monitoring and hardening MSSQL environments to prevent potential exploitation as described in the referenced content.
A high-severity vulnerability in Microsoft's WSUS (Windows Server Update Services) is being exploited by hackers to distribute the Skuld stealer malware despite the existence of a Microsoft patch. The flaw enables attackers to bypass patch protections and spread malicious payloads through WSUS infrastructure. Although the exploit is newly reported and discussion is minimal, the threat is significant due to WSUS's widespread use in enterprise environments for patch management. European organizations relying on WSUS for update deployment face risks of credential theft and data exfiltration from Skuld stealer infections. Mitigation requires immediate validation of patch application, enhanced WSUS security configurations, and network monitoring for anomalous WSUS traffic. Countries with large enterprise IT sectors and high WSUS adoption, such as Germany, France, and the UK, are most likely to be impacted. The threat is assessed as high severity given the potential for widespread compromise, ease of exploitation via trusted update channels, and the critical nature of stolen credentials. Defenders must prioritize patch verification, restrict WSUS access, and deploy endpoint detection to counter this evolving threat.
The APT group Cloud Atlas has launched a new wave of cyberattacks targeting Russia's defense industry. They are using stolen document templates from previously infected organizations to create malicious Microsoft Office files. The group cleans metadata from these documents to avoid revealing compromised entities. They move between targeted companies using compromised email accounts (BEC attacks). The attacks focus on defense industry enterprises, with malicious documents disguised as invitations, anti-corruption checks, mobilization documents, employee records, and financial statements. Cloud Atlas uses Google Sheets API for data exfiltration and employs the PowerShower backdoor. The group's infrastructure has migrated to new servers and domains, indicating ongoing campaign development.
The eRoom – Webinar & Meeting Plugin for Zoom, Google Meet, Microsoft Teams plugin for WordPress is vulnerable to exposure of sensitive information in all versions up to, and including, 1.5.6. This is due to the plugin exposing Zoom SDK secret keys in client-side JavaScript within the meeting view template. This makes it possible for unauthenticated attackers to extract the sdk_secret value, which should remain server-side, compromising the security of the Zoom integration and allowing attackers to generate valid JWT signatures for unauthorized meeting access.
A critical remote code execution vulnerability was discovered in Windows Server Update Services (WSUS), prompting Microsoft to release emergency patches. The flaw allows attackers to execute arbitrary code on affected Windows Server systems running WSUS, potentially leading to full system compromise. A proof-of-concept exploit has been publicly disclosed, increasing the urgency for organizations to apply the patch. Although no widespread exploitation has been observed yet, the presence of a PoC exploit raises the risk of imminent attacks. European organizations relying on WSUS for patch management are at significant risk, especially those with large Windows Server deployments. The vulnerability impacts confidentiality, integrity, and availability, as attackers can gain control over update infrastructure. Mitigation requires immediate deployment of the official Microsoft patches, enhanced monitoring of WSUS servers, and restricting network access to WSUS management interfaces. Countries with extensive Windows Server usage and critical infrastructure relying on WSUS, such as Germany, France, and the UK, are most likely to be targeted. Given the ease of exploitation and critical impact, this vulnerability is assessed as critical severity. Defenders must prioritize patching and implement compensating controls to prevent exploitation.
Tykit is a newly identified phishing kit targeting Microsoft 365 accounts, active since May 2025. It uses SVG files as delivery vectors and a multi-stage attack chain to mimic Microsoft login pages and steal credentials. The kit employs evasion techniques including Cloudflare Turnstile anti-bot protection and basic anti-debugging measures. It primarily targets industries such as finance, construction, IT, professional services, government, and telecom, with victims globally including the EMEA region. Stolen credentials are exfiltrated via API calls to attacker-controlled servers. The campaign requires user interaction through phishing but does not require prior authentication. This threat poses a medium severity risk due to its potential impact on confidentiality and the widespread use of Microsoft 365 in Europe.
GlassWorm is a groundbreaking self-propagating worm targeting VS Code extensions on OpenVSX marketplace. It employs invisible Unicode characters to conceal malicious code and utilizes a blockchain-based command and control infrastructure on Solana. The worm compromised seven OpenVSX extensions with 35,800 downloads, harvesting NPM, GitHub, and Git credentials, targeting cryptocurrency wallets, deploying SOCKS proxy servers, and installing hidden VNC servers. It spreads exponentially through the developer ecosystem using stolen credentials. The worm employs a triple-layer C2 setup involving Solana blockchain, direct IP connection, and Google Calendar. A new infected extension was also detected in Microsoft's VSCode marketplace. The campaign remains active, necessitating immediate security measures and audits of installed extensions.
A Deserialization of Untrusted Data vulnerability exists in the Apache ActiveMQ NMS AMQP Client.
This issue affects all versions of Apache ActiveMQ NMS AMQP up to and including 2.3.0, when establishing connections to untrusted AMQP servers. Malicious servers could exploit unbounded deserialization logic present in the client to craft responses that may lead to arbitrary code execution on the client side.
Although version 2.1.0 introduced a mechanism to restrict deserialization via allow/deny lists, the protection was found to be bypassable under certain conditions.
In line with Microsoft’s deprecation of binary serialization in .NET 9, the project is evaluating the removal of .NET binary serialization support from the NMS API entirely in future releases.
Mitigation and Recommendations:
Users are strongly encouraged to upgrade to version 2.4.0 or later, which resolves the issue. Additionally, projects depending on NMS-AMQP should migrate away from .NET binary serialization as part of a long-term hardening strategy.
CVE-2025-59250 is an improper input validation vulnerability in the Microsoft SQL Server JDBC Driver that allows unauthorized attackers to perform network spoofing. The flaw affects multiple versions of the driver prior to their respective fixed releases. This vulnerability has a high severity score of 8.1 and impacts confidentiality and integrity but not availability. Fixed versions have been released by the vendor.
Microsoft Defender has mistakenly flagged Microsoft SQL Server as an end-of-life product, causing potential false positive alerts in security monitoring. This misclassification does not represent a direct vulnerability or exploit but may lead to operational disruptions or misinformed patching decisions. No known exploits are associated with this issue, and it primarily affects organizations relying on Microsoft Defender for endpoint protection. European organizations using SQL Server could experience unnecessary remediation efforts or alert fatigue. The issue stems from incorrect product lifecycle data within Defender's detection logic. Mitigation involves verifying product lifecycle status through official Microsoft channels and adjusting Defender policies to prevent false alerts. Countries with significant Microsoft SQL Server deployments and strong Defender usage, such as Germany, the UK, France, and the Netherlands, are more likely to be impacted. The severity is assessed as medium due to the operational impact rather than a direct security compromise. Defenders should focus on validating alerts and maintaining accurate asset inventories to avoid unnecessary incident responses.
Medusa ransomware is reported to be exploiting a vulnerability in the GoAnywhere Managed File Transfer (MFT) software, as confirmed by Microsoft. This exploitation allows attackers to deploy ransomware payloads, potentially encrypting critical files and demanding ransom payments. Although no specific affected versions or CVEs have been disclosed, the threat is considered medium severity due to the potential impact on confidentiality, integrity, and availability of data. The attack vector involves leveraging a flaw in a widely used enterprise file transfer solution, which is common in European organizations for secure data exchange. No known exploits in the wild have been confirmed yet, but the threat is newsworthy and emerging. European organizations using GoAnywhere MFT should prioritize patching and monitoring for suspicious activity. Countries with significant adoption of GoAnywhere MFT and critical infrastructure relying on secure file transfers are at higher risk. Mitigation includes applying vendor patches once available, restricting network access to MFT servers, implementing robust backup strategies, and enhancing detection capabilities for ransomware behaviors. Given the medium severity, proactive defense is essential to prevent potential ransomware incidents impacting business continuity and data security.
A Chinese cybercrime group is operating a global SEO fraud campaign by compromising Microsoft IIS web servers. The attackers leverage these compromised servers to manipulate search engine rankings, likely redirecting traffic or injecting fraudulent content to benefit their SEO schemes. This campaign is high priority due to its global scale and the widespread use of IIS servers. Although no specific exploited vulnerabilities or CVEs are identified, the threat involves unauthorized access and control over web infrastructure, impacting confidentiality and integrity. European organizations running IIS servers are at risk of having their web assets abused for fraudulent purposes, potentially damaging reputation and causing indirect financial losses. Mitigation requires proactive server hardening, continuous monitoring for unauthorized changes, and rapid incident response. Countries with significant IIS deployment and high-value web infrastructure, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. Given the ease of exploitation implied by compromised servers and the broad impact on availability and integrity, the suggested severity is high. Defenders should prioritize detection of unusual web server activity and ensure robust patching and access controls to prevent compromise.
This update for rclone fixes the following issues:
Changes in rclone:
- Update to version 1.73.5:
* Version v1.73.5
* operations: add AuthRequired to operations/fsinfo to prevent backend creation CVE-2026-41179
* rc: snapshot NoAuth at startup to prevent runtime auth bypass CVE-2026-41176
* rc: add AuthRequired to options/set to prevent auth bypass CVE-2026-41176
* s3: fix empty delimiter parameter rejected by Archiware P5 server
* azureblob/auth: add Microsoft Partner Network User-Agent prefix
* drime: fix User.EntryPermissions JSON unmarshalling
* filter: fix debug logs that fire before logger is configured - fixes #9291
* s3: fix TencentCOS CDN endpoint failing on bucket check
* iclouddrive: fix 'directory not found' error when the directory contains accent marks
* Start v1.73.5-DEV development
- Update to version 1.73.4:
* Version v1.73.4
* Update to go 1.25.9 to fix multiple CVEs
* build: fix Denial of Service due to Panic in AWS SDK for Go v2 SDK EventStream Decoder
* docs: fix markdown issues in mount docs
* docs: fix header level for metadata option
* fix(docs): Fix link to not be language specific
* filen: update SDK version
* build(deps): bump golang.org/x/image from 0.36.0 to 0.38.0
* docs: note macOS 10.15 (Catalina) support with version v1.70.3
* Start v1.73.4-DEV development
- Update to version 1.73.3: (CVE-2026-33186 GHSA-6g7g-w4f8-9c9x)
* Version v1.73.3
* build(deps): bump github.com/buger/jsonparser from 1.1.1 to 1.1.2
* docs/jottacloud: fix broken link
* docs: clarify Filen password change requires updating both password and API key in rclone config
* docs: note that Filen API key changes on password change
* build(deps): bump google.golang.org/grpc from 1.79.1 to 1.79.3
* s3: add multi tenant support for Cubbit
* lib/rest: fix URLPathEscapeAll breaking WebDAV servers (eg nzbdav) with strict path matching
* list: fix nil pointer panic in Sorter when temp file creation fails
* docs: update RELEASE procedure to avoid mistakes
* docs: added text to the label showing version-introduced info
* Start v1.73.3-DEV development
* docs: update sponsors
- Update to version 1.73.2:
* Version v1.73.2
* Update to go 1.25.8 to fix multiple CVEs
* build: update to golang.org/x/net v0.51.0 to fix CVE-2026-27141 #9220
* docs: fix new drive flag typo in changelog
* webdav: add missing headers for CORS
* docs: Document unsupported S3 object keys with double slashes
* docs: note that --use-server-modtime only works on some backends
* internxt: fix Entry doesn't belong in directory errors on windows
* drime: fix chunk-uploaded files ignoring workspace ID
* docs: Fix headers hierarchy for mount.md
* webdav: escape reserved characters in URL path segments
* bisync: add group Sync to the bisync command
* archive: extract: strip "./" prefix from tar entry paths
* docs: add instructions on how to update Go version
* buid: update github.com/cloudflare/circl to v1.6.3 to fix CVE-2026-1229
* Start v1.73.2-DEV development
- Update to version 1.73.1:
* Version v1.73.1
* build: fix build using go 1.26.0 instead of go 1.25.7
* fs/march: fix runtime: program exceeds 10000-thread limit
* accounting: fix missing server side stats from core/stats rc
* pacer: re-read the sleep time as it may be stale
* pacer: fix deadlock between pacer token and --max-connections
* build: fix CVE-2025-68121 by updating go to 1.25.7 or later - fixes #9167
* drime: fix files and directories being created in the default workspace
* docs: update sponsors
* copyurl: Extend copyurl docs with an example of CSV FILENAMEs starting with a path.
* internxt: implement re-login under refresh logic, improve retry logic - fixes #9174
* docs: add ExchangeRate-API as a sponsor
* build: bump github.com/go-chi/chi/v5 from 5.2.3 to 5.2.5 to fix GO-2026-4316
* Set list_version to 2 for FileLu S3 configuration
* filelu: add multipart upload support with configurable cutoff
* filelu: add multipart init response type
* filelu: add comment for response body wrapping
* filelu: avoid buffering entire file in memory
* docs: update sponsor logos
* filen: fix potential panic in case of error during upload
* filen: fix 32 bit targets not being able to list directories Fixes #9142
* Start v1.73.1-DEV development
- Update to version 1.73.0:
* Version v1.73.0
* drive: fix crash when trying to creating shortcut to a Google doc
* azureblob,azurefiles: factor the common auth into a library
* test: allow backends to return fs.ErrorCantListRoot to skip Root tests
* build: add privatebeta Makefile target
* docs: add Internxt as a sponsor
* internxt: remove use of CVE laden github.com/disintegration/imaging
* docs: fix Internxt docs after merge
* docs: update making a new backend docs
* docs: build overview page from the backend data
* docs: add tiering to the documentation - fixes #8873
* docs: add data about ea
SMB Server might be susceptible to relay attacks depending on the configuration. An attacker who successfully exploited these vulnerabilities could perform relay attacks and make the users subject to elevation of privilege attacks.
The SMB Server already supports mechanisms for hardening against relay attacks:
SMB Server signing
SMB Server Extended Protection for Authentication (EPA)
Microsoft is releasing this CVE to provide customers with audit capabilities to help them to assess their environment and to identify any potential device or software incompatibility issues before deploying SMB Server hardening measures that protect against relay attacks.
If you have not already enabled SMB Server hardening measures, we advise customers to take the following actions to be protected from these relay attacks:
Assess your environment by utilizing the audit capabilities that we are exposing in the September 2025 security updates. See Support for Audit Events to deploy SMB Server Hardening—SMB Server Signing & SMB Server EPA.
Adopt appropriate SMB Server hardening measures.
Improper neutralization of special elements used in a command ('command injection') in SQL Server allows an authorized attacker to elevate privileges over a network.
Amazon's threat intelligence team has uncovered and disrupted a watering hole campaign conducted by APT29, a Russian threat actor. The campaign involved compromising legitimate websites to redirect visitors to malicious infrastructure, tricking users into authorizing attacker-controlled devices through Microsoft's device code authentication flow. This opportunistic approach demonstrates APT29's evolving tactics in scaling their operations for intelligence collection. The group employed techniques such as injecting obfuscated JavaScript, rapidly adapting infrastructure when faced with disruption, and using server-side redirects. Amazon's response included isolating affected EC2 instances, partnering with providers to disrupt domains, and sharing information with Microsoft. The article provides recommendations for user and organizational protection against such attacks.