ZeroDay Findings
Sign inSign up

Every 4 hours

Cyber

Keywords match titles. Record type separates incidents, intel, and research from CVEs.

  1. Research · Oct 16, 2026 · SecurityWeek

    BAE Systems Cyber Incident Disrupts Bankruptcy Court Notifications

    A recent cyber incident involving BAE Systems has caused significant disruptions in the Bankruptcy Noticing Center, affecting notifications across the United States.

    What changed

    A cyber incident at BAE Systems has led to the temporary shutdown of the Bankruptcy Noticing Center, resulting in a nationwide halt of notices for a week. This disruption has significant implications for legal and financial processes reliant on timely notifications.

    • The Bankruptcy Noticing Center is currently unable to process or send out notifications.
    • The incident has raised concerns about the security measures in place for critical infrastructure.
    • Legal proceedings may be delayed due to the lack of notifications.

    Who is affected

    The impact of this incident extends to various stakeholders within the legal and financial sectors.

    Entities relying on the Bankruptcy Noticing Center for timely notifications are particularly vulnerable.

    • Bankruptcy courts across the United States.
    • Legal professionals who depend on timely notifications for case management.
    • Financial institutions involved in bankruptcy proceedings.

    What to do

    Organizations and individuals relying on the Bankruptcy Noticing Center should prepare for potential delays in notifications and adjust their timelines accordingly.

    It is advisable to monitor updates from BAE Systems and relevant legal authorities regarding the restoration of services.

    • Stay informed about the status of the Bankruptcy Noticing Center's operations.
    • Consider alternative methods for tracking bankruptcy notifications during this downtime.
    • Review internal processes to mitigate the impact of such disruptions in the future.

    Original report

  2. Research · Oct 16, 2026 · CSO Online

    Critical Vulnerability in Linux Kernel Allows VM Escape

    A severe flaw in the Linux kernel has been patched, preventing potential guest-to-host escape attacks that could compromise system integrity.

    What changed

    The Linux kernel has been updated to address a critical vulnerability tracked as CVE-2026-99999, which allowed attackers to escape from a virtual machine (VM) to the underlying host. This flaw, known as PwnEscape, involved manipulating packet metadata to alter an IPv4 header after processing, potentially leading to host-level code execution.

    • The vulnerability was discovered during Vercel’s Sandbox security challenge.
    • The issue was classified as the most severe finding reported in the challenge.
    • The flaw has now been resolved with multiple stable-branch fixes released.

    Who is affected

    Organizations utilizing affected versions of the Linux kernel in their virtualized environments may be at risk. The vulnerability primarily impacts those running specific kernel versions.

    • Users of Linux kernel versions 5.10, 5.15, 6.1, 6.6, 6.12, 6.18, and 7.2.
    • Cloud service providers using virtualization technologies based on the Linux kernel.
    • Developers and researchers participating in sandbox environments like Vercel's.

    What to do

    It is imperative for affected organizations to update their Linux kernel to the latest patched versions to mitigate the risk associated with this vulnerability. Regular monitoring for security updates and vulnerabilities is also recommended.

    • Upgrade to the latest stable versions of the Linux kernel as specified in the NVD.
    • Review and enhance security measures for virtualized environments.
    • Stay informed about future vulnerabilities and participate in security challenges to test system defenses.

    Original report