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.
Active Directory (AD) domain join accounts, commonly used during system build processes, are frequently exposed and inherit over-privileged access control lists (ACLs). These excessive permissions enable attackers to exploit Local Administrator Password Solution (LAPS) disclosures, Resource-Based Constrained Delegation (RBCD), and other high-impact attacks. Even with Microsoft's recommended mitigations, residual risks remain due to replication lag and Active Directory Certificate Services (AD CS) interactions that can allow recovery of pre-reset machine secrets. Hardening requires layered controls including restricting machine account creation to privileged users, ensuring Domain Admins own computer objects, and applying deny Access Control Entries (ACEs) for sensitive attributes like ms-Mcs-AdmPwd and msDS-AllowedToActOnBehalfOfOtherIdentity. The threat is high severity due to the potential for privilege escalation and lateral movement within AD environments. Detection and mitigation require careful monitoring and tailored ACL configurations. European organizations relying heavily on AD infrastructure are at risk, especially those with complex domain join automation and build pipelines. Countries with large enterprise sectors and advanced IT infrastructure such as Germany, France, the UK, and the Netherlands are likely most affected. The threat is rated high severity due to the broad impact on confidentiality, integrity, and availability, ease of exploitation via exposed accounts, and the critical role of AD in enterprise security.
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.
The U. S. Cybersecurity and Infrastructure Security Agency (CISA) has added multiple vulnerabilities affecting Oracle, Mozilla, Microsoft Windows, the Linux Kernel, and Microsoft Internet Explorer to its Known Exploited Vulnerabilities catalog. These vulnerabilities are recognized as actively exploited or pose a significant risk, prompting increased attention for remediation. Although no specific CVSS scores or detailed technical exploit information are provided, the inclusion in CISA's catalog indicates a medium severity level with potential impacts on confidentiality, integrity, and availability. European organizations using these widely deployed software products are at risk, especially those in critical infrastructure, government, and large enterprises. Mitigation requires prioritizing patch management, monitoring for exploitation attempts, and applying vendor advisories promptly. Countries with high adoption of these technologies and strategic importance in digital infrastructure, such as Germany, France, the UK, and the Netherlands, are likely to be most affected. Given the broad scope and active exploitation potential, the suggested severity is medium. Defenders should focus on rapid vulnerability assessment and remediation to reduce exposure.
A critical vulnerability in the GoAnywhere managed file transfer software has been exploited in active ransomware attacks, as reported by Microsoft and covered by BleepingComputer. The flaw allows attackers to execute arbitrary code remotely, enabling ransomware deployment without requiring user interaction or authentication. This vulnerability poses a significant risk to organizations relying on GoAnywhere for secure file transfers, potentially leading to data encryption, operational disruption, and financial loss. European organizations using GoAnywhere are at heightened risk, especially in countries with high adoption of this software in critical infrastructure and enterprise sectors. Immediate patching and enhanced network monitoring are essential to mitigate exploitation. Due to the critical nature and ease of exploitation, this threat demands urgent attention from cybersecurity teams across Europe.
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.
A high-severity security flaw has been identified in the Unity game engine, as warned by Steam and Microsoft, potentially exposing gamers to cyberattacks. This vulnerability could allow attackers to exploit weaknesses in Unity-based games, leading to unauthorized code execution or data compromise. Although no known exploits are currently active in the wild, the flaw poses significant risks due to Unity's widespread use in game development. European organizations involved in gaming, game distribution, or related services may face increased risks, especially those with large user bases or development teams using Unity. Mitigation requires prompt patching once updates are available, enhanced monitoring of game-related network traffic, and applying strict security controls around game execution environments. Countries with strong gaming industries and large gamer populations, such as Germany, France, and the UK, are more likely to be affected. Given the potential for high impact on confidentiality and integrity, ease of exploitation, and broad scope, the suggested severity is high. Defenders should prioritize awareness, patch management, and user education to reduce exposure.
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
This takes "Single Sign-On" to a whole new level...
It's not about blaming Microsoft or any one vendor, but questioning why our systems are architected so a single platform can wield this kind of control in the first place.
We've written up a perspective on the broader implications and proposed how identity could be built differently. Full disclosure: we're the researchers/devs behind this piece, sharing our own analysis (hopefully this isn't taken as promotional to our non-commercial solution)
RaccoonO365 Phishing Network Dismantled as Microsoft, Cloudflare Take Down 338 Domains
Source: https://thehackernews.com/2025/09/raccoono365-phishing-network-shut-down.html
CVE-2024-7598 is a vulnerability in Microsoft software involving a race condition during namespace termination that allows bypassing network restrictions. The flaw affects specific versions 2.0 and 3.0 of the product. A patch is available to address this issue. There are no known exploits in the wild at this time.