A remote code execution (RCE) vulnerability has been identified in ImunifyAV, a widely used antivirus and security solution for Linux hosting environments. This flaw potentially allows attackers to execute arbitrary code on affected systems, putting millions of Linux-hosted websites at risk. Although no known exploits are currently active in the wild, the high severity rating and the nature of the vulnerability demand immediate attention. The vulnerability could lead to full system compromise, data theft, or service disruption. European organizations relying on Linux hosting with ImunifyAV installed are particularly vulnerable, especially those in countries with significant web hosting industries. Mitigation requires prompt patching once updates are available, restricting access to ImunifyAV interfaces, and monitoring for suspicious activity. Countries with large hosting markets and critical infrastructure, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. Due to the potential for complete system takeover without user interaction or authentication, the suggested severity is critical. Defenders should prioritize vulnerability assessment and containment measures to prevent exploitation.
Astro is a web framework. In Astro versions 2.16.0 up to but excluding 5.15.5 which utilizeon-demand rendering, request headers `x-forwarded-proto` and `x-forwarded-port` are insecurely used, without sanitization, to build the URL. This has several consequences, the most important of which are: middleware-based protected route bypass (only via `x-forwarded-proto`), DoS via cache poisoning (if a CDN is present), SSRF (only via `x-forwarded-proto`), URL pollution (potential SXSS, if a CDN is present), and WAF bypass. Version 5.15.5 contains a patch.
A malicious Visual Studio Code (VS Code) extension named 'Vibe-Coded' has been discovered containing built-in ransomware capabilities. This threat involves a seemingly legitimate extension that, once installed, can encrypt user files and demand ransom, leveraging the widespread use of VS Code among developers. Although no known exploits in the wild have been reported yet, the presence of ransomware functionality within a popular development tool extension poses a significant risk. European organizations using VS Code, especially those in software development and IT sectors, could face data loss and operational disruption. The threat is rated as high severity due to the potential impact on confidentiality, integrity, and availability of data, combined with the ease of exploitation through user installation. Mitigation requires strict extension vetting policies, use of trusted sources only, and enhanced endpoint protection with behavioral detection. Countries with large tech industries and high VS Code adoption, such as Germany, France, the UK, and the Netherlands, are most likely to be affected. Immediate awareness and proactive defense measures are critical to prevent compromise from this emerging ransomware threat.
The Medusa ransomware group has leaked 834 GB of sensitive Comcast data following a failed $1.2 million ransom demand. This incident highlights the growing threat of ransomware attacks targeting large corporations and the potential exposure of vast amounts of confidential data. The leak indicates a compromise of Comcast's internal systems, potentially impacting customer privacy and corporate operations. Although no specific exploited vulnerabilities or affected software versions are detailed, the attack underscores the importance of robust cybersecurity defenses against ransomware. European organizations should be aware of similar tactics as ransomware groups often target multinational companies. The threat is rated medium severity due to the significant data exposure but lacks details on exploitation complexity or direct impact on availability. Mitigation requires advanced detection, incident response readiness, and data protection strategies. Countries with major telecommunications sectors and large corporate infrastructures are more likely to be affected by similar threats. Overall, this ransomware incident serves as a critical reminder of the risks posed by extortion-based cyberattacks and the need for proactive defense measures.
The Clop ransomware group has claimed responsibility for a cyberattack targeting Harvard University. This incident involves unauthorized access and potential data encryption or exfiltration by a known ransomware threat actor. While specific technical details about the attack vector or exploited vulnerabilities are not provided, Clop is recognized for leveraging phishing, exploiting vulnerabilities, and deploying ransomware to disrupt operations and demand ransom payments. The attack highlights ongoing risks to academic institutions, which often hold valuable research data and personal information. European organizations, especially universities and research centers, face similar threats due to comparable data assets and network environments. Mitigation requires tailored defenses including enhanced email security, network segmentation, and proactive threat hunting. Countries with significant academic and research infrastructure, such as the UK, Germany, France, and the Netherlands, are more likely to be impacted. Given the medium severity rating and lack of detailed exploitation data, the threat is assessed as high severity due to ransomware’s potential for significant operational disruption and data compromise without requiring user interaction once inside. Defenders should prioritize detection and response capabilities to mitigate such ransomware threats effectively.
Astro is a web framework. Prior to version 5.14.2, Astro reflects the value in `X-Forwarded-Host` in output when using `Astro.url` without any validation. It is common for web servers such as nginx to route requests via the `Host` header, and forward on other request headers. As such as malicious request can be sent with both a `Host` header and an `X-Forwarded-Host` header where the values do not match and the `X-Forwarded-Host` header is malicious. Astro will then return the malicious value. This could result in any usages of the `Astro.url` value in code being manipulated by a request. For example if a user follows guidance and uses `Astro.url` for a canonical link the canonical link can be manipulated to another site. It is theoretically possible that the value could also be used as a login/registration or other form URL as well, resulting in potential redirecting of login credentials to a malicious party. As this is a per-request attack vector the surface area would only be to the malicious user until one considers that having a caching proxy is a common setup, in which case any page which is cached could persist the malicious value for subsequent users. Many other frameworks have an allowlist of domains to validate against, or do not have a case where the headers are reflected to avoid such issues. This could affect anyone using Astro in an on-demand/dynamic rendering mode behind a caching proxy. Version 5.14.2 contains a fix for the issue.
XWorm malware has reemerged with a new ransomware module and an expanded arsenal of over 35 plugins, enhancing its capabilities for persistence, data theft, and system compromise. Although no known exploits are currently active in the wild, the malware's modular architecture and ransomware addition significantly increase its threat potential. European organizations face heightened risks due to the malware's ability to disrupt operations, exfiltrate sensitive data, and demand ransom payments. Mitigation requires proactive network monitoring, strict endpoint security controls, and rapid incident response planning tailored to detect and contain modular malware behaviors. Countries with high adoption of Windows-based enterprise environments and critical infrastructure sectors, such as Germany, France, the UK, and the Netherlands, are particularly vulnerable. Given the malware's complexity, potential for widespread impact, and ease of deployment without requiring user interaction, the threat severity is assessed as high. Defenders should prioritize detection of unusual plugin activity and ransomware behaviors associated with XWorm to prevent significant operational and financial damage.
In the Linux kernel, the following vulnerability has been resolved: iommu/s390: Fix memory corruption when using identity domain zpci_get_iommu_ctrs() returns counter information to be reported as part of device statistics; these counters are stored as part of the s390_domain. The problem, however, is that the identity domain is not backed by an s390_domain and so the conversion via to_s390_domain() yields a bad address that is zero'd initially and read on-demand later via a sysfs read. These counters aren't necessary for the identity domain; just return NULL in this case. This issue was discovered via KASAN with reports that look like: BUG: KASAN: global-out-of-bounds in zpci_fmb_enable_device when using the identity domain for a device on s390.
Cisco Talos Incident Response has observed attacks by Chaos, a new ransomware-as-a-service group conducting big-game hunting and double extortion attacks. The group uses spam flooding, voice-based social engineering, RMM tool abuse, and legitimate file-sharing software for data exfiltration. Their ransomware employs multi-threaded rapid selective encryption and anti-analysis techniques, targeting both local and network resources. Chaos is likely formed by former BlackSuit (Royal) gang members, based on similarities in encryption methodology, ransom note structure, and toolset. The group has impacted various business verticals, predominantly in the U.S., UK, New Zealand, and India. They use the '.chaos' file extension and demand ransoms around $300K, threatening data disclosure and DDoS attacks if not paid.
Astro is a web framework for content-driven websites. In versions of astro before 5.13.2 and 4.16.18, the image optimization endpoint in projects deployed with on-demand rendering allows images from unauthorized third-party domains to be served. On-demand rendered sites built with Astro include an /_image endpoint which returns optimized versions of images. A bug in impacted versions of astro allows an attacker to bypass the third-party domain restrictions by using a protocol-relative URL as the image source, e.g. /_image?href=//example.com/image.png. This vulnerability is fixed in 5.13.2 and 4.16.18.
A sophisticated ransomware campaign has been uncovered, masquerading as a new SAP Ariba tool. The attack uses email lures, sender spoofing, and impersonation of legitimate software vendors to deliver LeeMe Ransomware. The malware employs SAP branding, a fake GUI, and a Portuguese ransom note. It targets various file types using AES-256 encryption and includes keylogging and data exfiltration capabilities. The ransomware creates autorun entries, bypasses Windows Defender, and sets up remote access. With a relatively low ransom demand, it appears to be a widespread campaign rather than targeting high-value individuals. The attack serves as a reminder of the importance of user vigilance and proper cybersecurity measures.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CreativeMindsSolutions CM On Demand Search And Replace cm-on-demand-search-and-replace allows Stored XSS.This issue affects CM On Demand Search And Replace: from n/a through <= 1.5.2.
Cross-Site Request Forgery (CSRF) vulnerability in CreativeMindsSolutions CM On Demand Search And Replace cm-on-demand-search-and-replace allows Cross Site Request Forgery.This issue affects CM On Demand Search And Replace: from n/a through <= 1.5.2.
Astro is a web framework for content-driven websites. In versions 5.2.0 through 5.12.7, there is an Open Redirect vulnerability in the trailing slash redirection logic when handling paths with double slashes. This allows an attacker to redirect users to arbitrary external domains by crafting URLs such as https://mydomain.com//malicious-site.com/. This increases the risk of phishing and other social engineering attacks. This affects sites that use on-demand rendering (SSR) with the Node or Cloudflare adapters. It does not affect static sites, or sites deployed to Netlify or Vercel. This issue is fixed in version 5.12.8. To work around this issue at the network level, block outgoing redirect responses with a Location header value that starts with `//`.
CVE-2025-38372 addresses a vulnerability in the Linux kernel's RDMA mlx5 driver related to unsafe xarray access in implicit On-Demand Paging (ODP) handling. The issue involved using __xa_store() and __xa_erase() functions without proper locking, causing lockdep warnings due to unsafe Read-Copy-Update (RCU) usage. The vulnerability has been fixed by replacing these calls with xa_store() and xa_erase(), which handle locking internally. The flaw could lead to kernel instability or crashes due to improper synchronization.