Vulnerabilities & CVEs

A newly disclosed vulnerability in the Linux kernel's vhost subsystem allows a local user to read and write kernel memory at will, escalating privileges to root across nearly a decade of kernel versions. Tracked as CVE-2026-74580 and named Vghost, the flaw was discovered by Tencent Zhuque Lab. Beyond straightforward local privilege escalation, the bug carries serious implications for virtualization environments. In at least one configuration, it allows an untrusted virtual machine to write to the host's memory and hijack the program responsible for running that VM — effectively breaking guest isolation and moving the attack from the guest out to the host. Key points: A local attacker can achieve arbitrary kernel memory read and write, leading to root. The vulnerability affects nearly a decade of kernel versions. In a virtualization setup, an untrusted VM can write to host memory and take over the VM runner, escaping the guest boundary. The flaw resides in the vhost subsystem. Given the long window of affected kernel versions and the potential for guest-to-host escape, administrators running multi-tenant or untrusted virtualization workloads should treat this as high priority and watch for vendor patches and updated kernel packages. Source: The Hacker News Does your organization run untrusted or multi-tenant VMs on affected kernels, and how are you planning to mitigate exposure until patches land?

SAP has released its October 2026 security updates, resolving 20 vulnerabilities across multiple products. Among them is a maximum-severity flaw in the Cloud SDK for Python. The critical issue is an OAuth2 server-side request forgery (SSRF) vulnerability, which SAP rates at the highest severity level. SSRF flaws of this kind can allow attackers to induce the application to send requests to unintended destinations, potentially reaching internal services that are not otherwise exposed. Details on the affected versions and the full list of patched issues are covered in SAP's security notes for this month. As always, administrators should review the October 2026 notes and apply the relevant fixes promptly. Apply the October 2026 SAP security updates without delay Prioritize the Cloud SDK for Python fix given its maximum severity rating Review SAP security notes for the complete list of the 20 patched vulnerabilities Organizations running the Cloud SDK for Python should treat this one as urgent. Source: Unknown Does your organization rely on the SAP Cloud SDK for Python, and have you already scheduled the October patches?

Docker has disclosed a critical vulnerability tracked as CVE-2026-105445 in Docker Hub that could have allowed attackers to access another user's container repositories by abusing a personal access token (PAT). By exploiting the flaw, an attacker could effectively impersonate a legitimate user and interact with their repositories as if they were the account owner. The most serious consequence is image tampering. Because access extended to repository contents, an attacker could potentially push modified images under a trusted account, opening the door to supply chain attacks against anyone pulling those images. This is especially concerning for organizations that rely on Docker Hub as part of their CI/CD pipelines or production deployments. At this stage, no specific affected version ranges, indicators of compromise, or patch KB numbers have been provided in the disclosure. Administrators should review their Docker Hub access logs and audit personal access tokens for any unexpected or unauthorized activity. Recommended steps: Rotate existing personal access tokens (PATs) and revoke any that are no longer needed Apply the principle of least privilege to token scopes, limiting write access where possible Review repository activity for unexpected pushes or tag changes Monitor Docker's official channels for further guidance and any patched releases Source: Unknown Has your organization reviewed its Docker Hub PAT scopes and repository activity since this disclosure?

A critical heap buffer overflow has been disclosed in Ghostscript, the widely used interpreter and rendering engine for PostScript and PDF files. Tracked as CVE-2026-39919, the flaw can be triggered through specially crafted PDF files and may allow attackers to achieve remote code execution on vulnerable systems. The risk is amplified by how commonly Ghostscript is embedded in server-side document processing pipelines. Any service that accepts user-supplied PDFs, or converts and previews documents, could potentially be abused as an entry point if it relies on an unpatched Ghostscript installation. In practice, this means a malicious file upload is all it takes to reach the vulnerable code path. Key points to be aware of: Vulnerability type: heap buffer overflow in Ghostscript Identifier: CVE-2026-39919 Attack vector: specially crafted PDF files Impact: potential remote code execution Exposure: server-side document processing and PDF upload/rendering features Administrators and developers should treat this as high priority. Recommended steps include applying the latest Ghostscript patches as soon as they are available, restricting or sandboxing document conversion services, and monitoring for suspicious PDF upload activity. If Ghostscript is bundled inside a larger application or container image, verify the embedded version rather than assuming it is current. Source: Unknown Does your organization process untrusted PDFs through Ghostscript, and if so, how are you handling exposure to CVE-2026-39919?

Microsoft's October 2026 Patch Tuesday is the largest on record, with security updates resolving 1,411 flaws. Among them are three zero-day vulnerabilities: one actively exploited in the wild and two publicly disclosed before a fix was available. This volume stands out even against Microsoft's typically heavy release cadence, and the presence of an actively exploited zero-day makes prompt patching a priority for administrators. Key points: Total flaws fixed: 1,411 Zero-days addressed: 3 Actively exploited zero-days: 1 Publicly disclosed zero-days: 2 Given the record scale of this release and the confirmed active exploitation, teams should treat this cycle as high urgency and prioritize internet-facing and commonly targeted systems first. Source: Unknown How is your organization approaching such a large patch load — staged rollout or emergency deployment across the board?

Microsoft has rolled out its latest Patch Tuesday cumulative updates for Windows 11, delivering fixes for security vulnerabilities and bugs alongside a set of new features. The updates arrive as KB5127648 and KB5126653, covering multiple branches of the operating system. The releases target the following versions: KB5127648 applies to Windows 11 versions 26H2, 25H2, and 24H2 KB5126653 applies to Windows 11 version 23H2 Administrators and home users running any of these builds should treat the updates as routine maintenance and plan to install them through their usual patching channels. As with any Patch Tuesday release, the security fixes included address vulnerabilities that could otherwise expose systems to exploitation, making timely deployment important. If your environment manages updates centrally, verify that your deployment rings or policies account for both KB numbers, since the version split means a single update won't cover every device. Source: Unknown Has your organization already pushed these updates, or are you holding them back for testing first?

Ivanti has issued an urgent warning to customers regarding an actively exploited zero-day vulnerability in its Connect Secure (ICS) remote access gateway. The company is urging immediate patching to address the issue. While specific technical details remain limited in the initial advisory, the critical takeaway is that this is a zero-day vulnerability currently being exploited in the wild. Organizations using Ivanti Connect Secure should treat this as a high-priority emergency. Review the official Ivanti advisory for the latest information. Apply the recommended patches or mitigations immediately. Monitor for any signs of compromise related to your Connect Secure appliances. Source: BleepingComputer Has your organization already applied the patch, or are you still assessing the impact on your environment?

Attackers are still finding plenty of room to operate in environments where MFA coverage is incomplete. The pattern is consistent: stolen credentials get used to log into VPNs, RDP endpoints, and Windows systems that still depend on passwords alone. Even organizations that have rolled out MFA for cloud applications remain exposed when on-premises and remote access paths are left out of scope. The core problem is that protecting cloud applications is not the same as protecting the whole identity surface. Legacy authentication protocols, direct remote access services, and local Windows logons often sit outside MFA enforcement, giving attackers a low-friction path once credentials are compromised. Key points from the report: Attackers are exploiting gaps in MFA coverage, not bypassing MFA everywhere. Stolen credentials are being reused against VPNs, RDP, and Windows systems that rely on passwords alone. Securing cloud applications alone leaves on-premises and remote access authentication unprotected. Closing these gaps requires extending MFA enforcement to all authentication paths, including legacy and remote access entry points. The takeaway for defenders is to audit where MFA is not enforced, particularly remote access and legacy authentication flows, and treat those as priority gaps rather than edge cases. Source: BleepingComputer Does your organization enforce MFA across VPN, RDP, and Windows logons, or are those still relying on passwords alone?

Google has paused product vulnerability reports through its bug bounty program for open-source software, effective October 1. Researchers can no longer submit security flaws found in the code of projects such as Go, Angular, and Protocol Buffers for a reward. A few important details about what still works: Reports about supply chain compromises are still accepted. Reports filed before October 1 remain in scope for review under the previous process. The change follows a surge in invalid automated reports, which appears to have pushed Google to narrow the program's intake while it reassesses how product-level findings in OSS code are handled. Source: The Hacker News Has your team adjusted its OSS disclosure workflow since this pause took effect?

If you're evaluating an agentic pentesting solution, you've likely encountered the same pitch more than once: point it at a target, and it autonomously discovers, validates, and exploits attack paths the way a real attacker would. That promise deserves serious consideration, but it also deserves pressure testing. Three questions do most of the work when assessing what an agentic pentesting tool actually proves and where its capabilities stop. The core appeal is straightforward. Rather than relying on human testers to manually chain together findings, an agentic system is marketed as being able to independently identify weaknesses, confirm they're exploitable, and demonstrate real-world impact without hand-holding. For security teams stretched thin, that's an attractive proposition. But the article cautions that the marketing narrative and the practical reality aren't always aligned. The key is understanding the boundaries of what such tools can demonstrate, and asking the right questions before trusting their output. What the assessment can actually achieve, how it validates findings, and where its autonomy ends are the critical areas to scrutinize. Without clear answers, you risk overestimating coverage or mistaking automated activity for genuine attacker emulation. Source: The Hacker News Has your organization trialed any agentic pentesting tools, and did the results match the vendor's claims?

Attackers moved within hours to exploit a newly disclosed security flaw this week — in some cases faster than defenders could finish reading the advisory, let alone patch. Speed remains only one part of the problem, though. A secure connection did not always guarantee a safe destination, and some parties offering to clean up ransomware incidents ended up facing questions of their own. The weekly roundup also covers helpdesk 0-days, rogue certificates, the ShinyHunters arrest, and malware designed to fool AI systems. Key developments this week: Helpdesk 0-days being exploited in the wild Rogue certificates undermining trust in secure connections An arrest tied to the ShinyHunters group Malware techniques crafted to evade or fool AI-based defenses The recurring theme: attackers are operating on a timeline measured in hours, while many organizations are still working through disclosure, triage, and remediation. Treat any newly published flaw as potentially under active exploitation from day one. Source: The Hacker News How is your organization handling the shrinking window between disclosure and exploitation?

GitLab has issued an urgent warning about a maximum-severity vulnerability in its CI/CD Regular Expression Compiler that could allow remote attackers to execute arbitrary code on affected instances. The company is advising all users to patch immediately. The flaw resides in the CI/CD regex compilation engine, and successful exploitation could give an unauthenticated attacker the ability to run code remotely on targeted GitLab installations. Given the severity rating, this is a high-priority patch for anyone running GitLab, whether self-managed or otherwise. At this time, no specific CVE identifier has been provided in the available reporting, so admins should refer directly to GitLab's official security advisory for the exact affected versions and fix details. Recommended actions: Update GitLab to the latest patched release as soon as possible Check GitLab's official security advisory for the precise affected version ranges Restrict or monitor exposed GitLab instances until patching is complete Source: BleepingComputer Has your organization already applied the patch, or are you still assessing exposure?

Threat actors have been observed exploiting a recently disclosed critical security flaw in SonicWall Secure Mobile Access (SMA) 1000 appliances within days of public disclosure. The vulnerability is tracked as CVE-2026-102255 and carries a CVSS score of 10.0. It is a pre-authenticated server-side request forgery (SSRF) issue that could allow a remote attacker to direct the appliance to issue requests on their behalf. Since the patch was released, roughly 135 exploitation attempts have been recorded against the flaw, underscoring how quickly attackers are moving to weaponize publicly disclosed issues in edge-facing appliances. Key points: Affected product: SonicWall SMA 1000 series appliances Vulnerability type: pre-authenticated SSRF Severity: CVSS 10.0 (critical) Activity observed: approximately 135 exploitation attempts following the patch If your organization runs SMA 1000 appliances, prioritize applying the vendor's fix and review exposure of the management interface to the public internet. Restricting access and monitoring for unusual outbound requests from the appliance can help reduce risk in the interim. Source: [email protected] (The Hacker News) Has your organization already patched its SonicWall SMA 1000 appliances, or are you still assessing exposure?

A maximum-severity vulnerability in the Bricksforge plugin for WordPress is now being actively exploited in the wild, according to Patchstack. The flaw, tracked as CVE-2026-85097, carries a CVSS score of 10.0, the highest possible severity rating. The issue allows unauthenticated attackers to upload and execute arbitrary PHP code on vulnerable WordPress sites, resulting in remote code execution (RCE). Because no authentication is required to trigger the flaw, any exposed installation running an affected version of the plugin is potentially at risk of full site compromise. Key points: Affected software: Bricksforge plugin for WordPress Identifier: CVE-2026-85097 Severity: CVSS 10.0 (critical) Impact: unauthenticated arbitrary PHP upload and execution, leading to RCE Status: active exploitation confirmed in the wild by Patchstack Site administrators running Bricksforge should treat this as urgent: verify whether the plugin is installed, check for any signs of unexpected file uploads or modified PHP files, and apply the vendor's fix or remove the plugin if no patch is available. Given the unauthenticated nature of the flaw, internet-facing instances should be prioritized for review. Source: The Hacker News Is your organization running Bricksforge, and if so, have you already patched or pulled the plugin?

A critical security issue has been identified in LMCache, an open-source caching layer used to accelerate large language model servers such as vLLM. According to the report, the flaw allows an unauthenticated attacker to execute code on the cache server, and as of now there is no fixed version available. The vulnerability resides in LMCache's multiprocess mode, where the cache operates as a standalone server that LLM workers connect to via the ZeroMQ messaging library. The article indicates that a single network interaction is enough to trigger the issue, meaning an attacker does not need credentials or prior access to the service. Because the cache server communicates directly with LLM workers, successful exploitation could give an intruder a foothold in the inference infrastructure. Key points from the report: Affected component: LMCache running in multiprocess mode Communication layer involved: ZeroMQ Attack vector: unauthenticated, remote Impact: arbitrary code execution on the cache server Patch status: no fixed version available at the time of reporting No specific CVE identifier, advisory number, or affected version list was provided in the source material, so none is cited here. Administrators running LMCache in multiprocess mode should treat this as a high-priority exposure and consider isolating cache servers from untrusted networks, restricting access to the ZeroMQ endpoints, and monitoring for unexpected connections until an official fix is released. Source: The Hacker News Is your organization running LMCache in multiprocess mode, and if so, what steps are you taking to limit exposure while no patch exists?

Threat actors are actively exploiting two recently disclosed vulnerabilities in the AhsayCBS backup utility to compromise affected devices, deploying web shells and XMRig cryptocurrency miners. The flaws allow attackers to gain control of vulnerable systems and establish persistence while quietly mining cryptocurrency in the background. The vulnerabilities in question are: CVE-2026-105133 (CVSS v4 score: 5.5) — an improper authentication vulnerability in the checkSysPwd() function within com/ahsay/obs/api/ApiStructsAction.java According to reporting, the second flaw was also disclosed alongside this one, though specific details on its identifier were not provided in the source material. Attackers have been observed chaining these issues to take over devices, drop web shells for continued access, and deploy XMRig miners that are disguised as Microsoft Edge to evade detection. Administrators running AhsayCBS should treat this as an urgent patching priority. Given the active exploitation in the wild, organizations using this backup solution should: Apply any available vendor patches or updates immediately Review systems for signs of compromise, including unexpected processes masquerading as Microsoft Edge Inspect for web shells and unauthorized scheduled tasks or services Monitor for unusual CPU usage that could indicate cryptomining activity Restrict network exposure of the AhsayCBS management interface where possible The use of legitimate-looking process names like Microsoft Edge is a common defense evasion technique, so security teams should not rely on process names alone when hunting for malicious activity. File paths, parent processes, and network connections should all be examined. Source: [email protected] (The Hacker News) Has anyone in the community seen signs of this exploitation in their environment, or does your organization rely on AhsayCBS for backups?

Citrix has released patches addressing a critical memory overflow vulnerability affecting NetScaler ADC and NetScaler Gateway. Tracked as CVE-2026-107406, the flaw can lead to remote code execution or denial-of-service under specific configuration conditions, according to Citrix. The vulnerability is particularly relevant to SAML deployments, where exploitation could potentially enable RCE. Citrix has not disclosed further technical details beyond the memory overflow nature of the flaw and the conditions required for exploitation. Affected products: NetScaler ADC NetScaler Gateway Administrators running these products, especially in SAML configurations, should review Citrix's advisory and apply the available patches as soon as possible. Given the severity of potential RCE, prioritising this update is strongly recommended. Source: The Hacker News Is your organisation running NetScaler in a SAML deployment, and have you already applied the patch?

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added five security flaws to its Known Exploited Vulnerabilities (KEV) catalog after they were abused by a China-linked threat actor tracked as Flax Typhoon. Among the entries is CVE-2015-3306, a critical improper access control vulnerability in ProFTPD carrying a CVSS score of 10.0. The flaw could allow attackers to compromise affected systems, and its presence in the KEV catalog confirms it has been exploited in the wild. Federal agencies are required to remediate the listed vulnerabilities by October 11, per the binding operational directive tied to the KEV catalog. Affected organizations should review their exposure to the following: ProFTPD — CVE-2015-3306 (CVSS 10.0), improper access control Given that Flax Typhoon is actively exploiting these flaws, defenders are urged to prioritize patching and to check for signs of compromise on any internet-facing services running the affected software. Source: The Hacker News Has your organization reviewed its KEV catalog obligations ahead of the October 11 deadline, and are any of your internet-facing services running the affected software?

A newly published vulnerability, tracked as CVE-2026-105133, has been identified in Ahsay AhsayCBS versions up to 10.3.2. The flaw affects the checkSysPwd function within the file com/ahsay/obs/api/ApiStructsAction.java, which is part of the API component. By manipulating the random argument, an attacker can trigger improper authentication. The vulnerability can be exploited remotely, and a public exploit is now available, meaning it could be used in active attacks. The issue is mitigated by upgrading to version 10.3.4, and upgrading the affected component is strongly recommended. Affected product: Ahsay AhsayCBS up to 10.3.2 Affected component: API (checkSysPwd function in com/ahsay/obs/api/ApiStructsAction.java) Exploit status: Publicly available Mitigation: Upgrade to 10.3.4 Source: NVD Has anyone running AhsayCBS already moved to 10.3.4, or are you seeing signs of exploitation attempts against the API?

Anthropic has introduced OSS Scanner, an opt-in vulnerability scanner that applies artificial intelligence to help protect the open-source ecosystem. The company announced the tool on Thursday, positioning it as a free service for projects that choose to take part. According to Anthropic, the scanner draws on the company's experience using Claude to uncover vulnerabilities during Project Glasswing. Projects that enroll will receive comprehensive, recurring security scans performed by Anthropic's most capable models, at no cost to the maintainers. Key points: OSS Scanner is an opt-in service, meaning projects must actively join to be scanned. Scans are periodic and performed by Anthropic's strongest models. The service is offered free of charge to participating open-source projects. The tool was informed by Anthropic's prior work using Claude to find vulnerabilities in Project Glasswing. Source: The Hacker News Would you trust AI-driven scanning to catch vulnerabilities in the open-source projects you depend on, or would you still want a human review in the loop?