In the Linux kernel, the following vulnerability has been resolved:
mailbox: mailbox-test: free channels on probe error
On probe error, free the previously obtained channels. This not only
prevents a leak, but also UAF scenarios because the client structure
will be removed nonetheless because it was allocated with devm.
A race condition vulnerability in the Linux kernel's netfilter synproxy infrastructure has been resolved by adding a mutex to guard hook reference counting. The issue occurred because netfilter hooks are registered on-demand when the first iptables target or nftables expression is added, and concurrent operations could race each other. The fix introduces a mutex to serialize access to the reference count control blocks, preventing race conditions.
When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.
A report surfaced on Reddit about a rootkit named '844ljfpvz.sys' that is signed with a WHQL Microsoft certificate. The information is limited and primarily sourced from a social media link without detailed technical analysis or vendor confirmation. No affected software versions or exploitation details are provided. The rootkit's Microsoft WHQL signature suggests it may bypass some security controls, but no official advisory or patch information is available.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security Fix(es):
* kernel: net/sched: act_pedit: extend the writable skb range per key (CVE-2026-46331)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
The public PoC code exploits a race condition in Microsoft Defender to spawn a command prompt with System privileges. The post Microsoft Working on Patch for ‘RoguePlanet’ Zero-Day appeared first on SecurityWeek .
A stack buffer overflow vulnerability exists in the SCTP error cause parsing within the inet_drv component of Microsoft software version 3.0. This flaw can be triggered remotely and may cause the targeted virtual machine to crash.
A vulnerability in Microsoft products version 3.0 and 4.0 allows a silent bypass of the Distribution-over-TLS LAN allowlist due to confusion between socket names and peer names in the inet_tls_dist component.
Discover how continuous control validation in Tenable One can improve your CTEM program by filtering out alert noise and factoring in your active cyber defenses. Focus your team on accessible and exploitable attack paths. Key takeaways: With vulnerability exploitation ranking as the top initial access vector and frontier AI accelerating vulnerability discovery, organizations must shift from managing theoretical cyber risks to validating actual, accessible exposure. Tenable One maps active security controls including EDR, MFA, and firewalls directly onto potential attack paths, allowing teams to automatically deprioritize weaknesses that existing defenses already neutralize. Ingesting penetration testing results via the Tenable One Open Connector allows organizations to layer real-world attack simulations over real-time exposure insights to identify toxic risk combinations that threaten critical assets. Your security tools probably indicate you have thousands, perhaps tens or hundreds of thousands, of vulnerabilities across your environment. Maybe your tools prioritize these vulnerabilities based on CVSS scores or other criteria, but how do you know which vulnerabilities combine with other preventable security risks, like misconfigured cloud buckets and identity weaknesses, to create attack paths threat actors could realistically traverse? How do you validate which vulnerabilities an existing security control mitigates? You need this context to distinguish the real risks from the theoretical ones to ensure your team focuses on remediating what matters most. The work of validating, prioritizing, and remediating vulnerabilities alongside other security weaknesses to understand the true exposure they create has become much more urgent, as frontier AI models accelerate vulnerability discovery. In this environment, the traditional patch-based defense model will get crushed. Moreover, defenders cannot afford inaccurate decision-making and wasted remediation work that addresses low-priority vulnerabilities. They desperately need the context and validation that a continuous threat exposure management (CTEM) program provides. This is why security leaders are evolving their vulnerability management programs to exposure management programs. Exposure management allows you to continually assess your attack surface, prioritize risks , and orchestrate automated remediation of security weaknesses at machine speed. Exposure management also helps validate which exposures attackers can actually reach by understanding the accessibility and exploitability of an attack path. It uses validation to shift your organization from managing theoretical risks to executing on actual exposure. What is exposure validation in CTEM? Validation is one of the five steps in the CTEM lifecycle. It is the process of providing consistent, continuous, and automated evidence of an attack’s feasibility. It stress-tests your defenses against real-world attack conditions, using your own environment’s controls and configurations to confirm whether an exposure is genuinely reachable and exploitable. Validation moves security from a reactive “patch everything” mindset to a preemptive, evidence-based exposure strategy . It continuously confirms which weaknesses your existing defenses have already blocked and surfaces the ones that demand immediate attention. Expanded CTEM validation capabilities in Tenable One Validation isn’t new to Tenable: we’ve been using validation techniques in Tenable solutions for more than 25 years. Tenable developed nearly 3,000 direct check plugins to actively probe a vulnerability and prove its exploitability in situations where software version detection isn’t sufficient for our high-accuracy standards. These plugins actually mimic attack techniques and monitor the target’s response to confirm the presence of the vulnerability. What is new in Tenable One is the addition of continuous control validation in the platform. By factoring in your active security controls, Tenable One helps eliminate the noise of theoretically exposed assets that are functionally blocked from exploitation. Security teams can visually map their active prevention and detection controls directly onto potential attack paths, automatically prioritizing weaknesses that existing controls already neutralize. Analysts can also filter top attack paths based on the presence of security controls and whether you can prevent attack chains for faster triage and investigation. Common control validation examples include: Endpoint detection and response (EDR) tools that block Local Security Authority Subsystem Service (LSASS) memory dump tools used to harvest credentials. Multi-factor authentication (MFA) methods that prevent unauthorized access via password guessing , password spraying , or credential stuffing . Firewall and data loss prevention (DLP) tools that prevent data exfiltration by detecting data staging and enforcing egress rules. See how continuous control validation works in Tenable One. Proactively manage risk prioritization with continuous security control validation. Eliminate noise from theoretical risks that are functionally blocked by existing defenses by integrating compensating security controls into the exposure prioritization process. Access a unified dashboard where assets, vulnerabilities, and exposure risks are consolidated. Filter attack paths to identify which are protected by compensating controls. View types of compensating controls deployed in the environment. Examine attack paths that could be protected with endpoint protection tools. Review security controls associated with specific attack paths, including SIEM and EDR controls. Inspect individual nodes within attack paths to determine which security controls are protecting them. Identify assets monitored by SIEM tools such as Splunk. Verify endpoint protection coverage on assets, including Microsoft Defender installations. Filter attack techniques to focus on specific threats like LSASS Memory techniques, which extract credentials from compromised systems and can be mitigated by endpoint protection tools. Identify attack paths and assets lacking appropriate EDR coverage. Prioritize remediation by examining high-priority attack paths where compensating controls are absent. Collaborate with security control owners to confirm coverage and address gaps in protection for critical assets. Integrate penetration testing data into Tenable One Beyond direct check plugins and continuous control validation, security teams can also integrate penetration testing results into Tenable One that simulate real-world attacks against your cyber defenses. This is another way to validate which exposures are truly exploitable and contextualizes them against your broader attack surface. The Tenable One Open Connector makes it easy to ingest the latest pentest results and layer them with real-time exposure insights to turn your findings into active, continuous defenses. Integrating pentest data into an exposure management program adds critical context to help you understand toxic risk combinations and enrich your understanding of high-severity weaknesses that threaten your most critical business assets. Context is essential in exposure management In the AI era, your security team can’t waste precious time on the wrong issues. With exposure management, context is essential to pinpoint the most critical risks to your organization. Security control validation, coupled with asset criticality, threat activity, entitlement privileges, and attack pathways, give your security team the advantage it needs to stay ahead of threat actors. Learn more about Tenable One , the exposure management platform for the modern attack surface.
RoguePlanet is a reported Windows zero-day vulnerability that abuses Microsoft Defender's own quarantine pipeline. The vulnerability was disclosed via a Reddit cybersecurity post linking to an external analysis by Cybereason's Howler Cell team. No detailed technical information, affected versions, or proof of exploitation in the wild have been provided. The threat is classified as critical based on the initial report but lacks official vendor confirmation or patch information.
Exploiting a race condition in Microsoft Defender, the exploit leads to local privilege escalation to SYSTEM. The post New Windows Zero-Day Exploit ‘RoguePlanet’ Released appeared first on SecurityWeek .
A zero-day vulnerability named RoguePlanet in Microsoft Defender allows attackers to gain SYSTEM-level access on fully updated Windows 10 and 11 machines. The exploit is a race condition that can result in arbitrary code execution with the highest privileges. It has been publicly disclosed with a proof-of-concept by a security researcher known as Chaotic Eclipse. The vulnerability affects desktop Windows systems with June 2026 Patch Tuesday updates installed but does not currently work on Windows Server due to mounting restrictions. The researcher has criticized Microsoft's handling of vulnerability disclosures and has released multiple related exploits. Microsoft has condemned the public disclosures but has not yet provided an official patch.
CVE-2026-46330 is a vulnerability related to Microsoft software version 3.0. The available information is limited and does not include technical details, CVSS score, or exploit data. No patch or remediation details are provided.
CVE-2026-46324 is a vulnerability related to netfilter's nf_tables component involving the use of list_del_rcu for netlink hooks. The advisory references Microsoft products, specifically version 3.0, but provides no detailed technical information or impact specifics. No CVSS score or exploit details are available.
A security researcher has released a new Microsoft Defender zero-day exploit named "RoguePlanet" just hours after Microsoft fixed two previously disclosed flaws during June 2026 Patch Tuesday. [...]
This content describes a practical detection approach for identifying encoded PowerShell commands using Kusto Query Language (KQL) in Microsoft Sentinel. The detection method incorporates a weighted scoring model that reduces noise by considering multiple indicators beyond the simple presence of encoded commands, such as the parent process, download-related keywords, execution flags, and execution paths. The approach aims to improve alert accuracy and reduce false positives in enterprise environments. It is not a vulnerability or exploit but a detection technique shared on a public forum.
Entra Agent ID objects are a new type of identity in Microsoft Entra ID that behave similarly to service principals. They have baseline protections such as blocking assignment of some highly privileged roles and Microsoft Graph API permissions. However, many powerful API permissions remain assignable, and because these objects can operate cross-tenant, risks like consent phishing persist. Certain roles and permissions related to agent identities and blueprints should be considered highly privileged due to their potential for takeover or control. Defensive focus should include monitoring privileged agent objects, blueprint ownership, credentials, inherited permissions, and cross-tenant usage.
This security news discusses HTTP/2 HPACK amplification attacks, also known as the "HTTP/2 bomb," which can cause large server-side memory allocations from small client requests. The research covers multiple HTTP/2 server implementations including nginx, Apache httpd, Envoy, Pingora, and Microsoft IIS. The authors provide detection signatures and verified mitigation directives, such as specific nginx and Apache configuration changes and version upgrades. Lab tests show significant amplification effects, with memory usage rising from megabytes of wire traffic to multiple gigabytes of server RAM. Fixes are available for nginx (version 1.29.8 and later) and Apache httpd (mod_http2 version 2.0.41 and later). The status of fixes for IIS, Envoy, and Pingora is currently unknown.