Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier permits arbitrary code execution in the context of the current user when a victim opens a crafted file. The flaw is local (AV:L), requires user interaction (UI:R), and needs no privileges (PR:N), so exploitation depends on social engineering rather than remote autonomous triggering. No public exploit or confirmed active exploitation (CISA KEV) is identified at time of analysis, making this a high-priority patch item but not an emergency per the independent assessment.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the user who opens a crafted file, and Adobe's PSIRT has published advisory APSB26-170 covering the issue. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) scores 7.8 High on the strength of full confidentiality, integrity and availability impact, but the attack is not remotely triggerable: the attacker must deliver a malicious file and convince a victim to open it, and any resulting code runs only with that user's privileges, with no privilege escalation beyond the current user. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV); exploitation is neither automatable nor network-reachable, so risk concentrates on targeted file-delivery campaigns against individual Stager users.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the current user when the victim opens a maliciously crafted 3D project or asset file. The attack path is local and requires user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8), with no network-facing trigger and no privilege escalation beyond the rights of the user who opens the file. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; this is a genuine but not emergency-grade priority, where the practical risk is driven by social engineering that convinces a Stager user to open attacker-supplied content.
Out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier allows arbitrary code execution in the context of the current user when a victim opens a crafted 3D asset or scene file. The flaw is a client-side file-parsing issue (CWE-787) with a local attack vector and required user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.8); no public exploit identified at time of analysis, and no confirmed active exploitation (CISA KEV). Attackers must deliver a malicious file to the target and induce the user to open it, which limits exposure to systems where untrusted Stager files are processed.
An out-of-bounds write in Adobe Substance 3D Stager 3.1.8 and earlier lets an attacker achieve arbitrary code execution in the context of the current user when a victim opens a specially crafted 3D project or asset file. The attack is local in nature (AV:L) and depends entirely on user interaction (UI:R) - the victim must be socially engineered into opening the malicious file - and the resulting code runs with the victim's own privileges rather than elevated rights (no privileges are required per PR:N). At time of analysis there is no public exploit identified and the issue is not listed in CISA KEV, so this is assessed as a moderate-priority, not emergency, memory-corruption flaw whose primary risk is targeted, file-based social engineering against individual Substance 3D Stager workstations.
Arbitrary code execution in Adobe Substance 3D Stager 3.1.8 and earlier is achievable when a user is persuaded to open a maliciously crafted file, allowing an unauthenticated attacker to corrupt memory out of bounds and run code in the context of the current user. The CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a local, file-based flaw with no network attack surface, where the mandatory user interaction of opening an untrusted file is the principal limiting factor; impact is confined to the victim user's privileges rather than the whole system. No public exploit code has been identified at time of analysis, and there is no CISA KEV entry indicating confirmed active exploitation.
Privilege escalation leading to remote code execution in Xen Orchestra deployments before 6.9.0 lets any authenticated account, regardless of how few permissions it holds, obtain global administrator rights. The vm.importFromEsxi and vm.importMultipleFromEsxi methods lack access-control checks, so an authenticated remote attacker who can make xo-server import from an attacker-controlled ESXi host serving a crafted .vmx file containing a __proto__.permission property pollutes Object.prototype; every permission-less account then inherits admin rights, and that administrative foothold enables remote code execution. The flaw is rated 7.7 (CVSS 4.0, AV:N/AC:H/PR:L) and assessed as CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; exploitation requires a valid low-privileged Xen Orchestra account plus control of the ESXi endpoint xo-server connects to, and no public exploit code was identified at time of analysis.
An out-of-bounds read in Microsoft SQL Server allows an authenticated, low-privileged database user to make the engine read past the bounds of an allocated buffer and disclose information over the network, affecting unpatched builds in the 2017, 2019, 2022 and 2025 release trains across both GDR and cumulative-update branches. The vector (AV:N, PR:L, UI:N, S:C, C:H, I:N, A:N) means the flaw needs only a valid login reachable on the TDS endpoint - no user interaction and no special configuration - but cannot be triggered by an unauthenticated remote attacker, and integrity and availability are unaffected. Vendor patches are available per the MSRC update guide, and no public exploit code or confirmed active exploitation was identified at time of analysis, so this is a credible but second-tier disclosure risk rather than an emergency zero-interaction issue.
Information disclosure in Microsoft SQL Server 2017, 2019, 2022, and 2025 allows an authenticated low-privilege attacker with network access to trigger an out-of-bounds read and potentially disclose sensitive memory contents. The affected builds are those in the EUVD-listed GDR and cumulative-update ranges, and the assessed vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, so valid database credentials and network reachability are required but no user interaction is needed. No public exploit has been identified at time of analysis, no CISA KEV listing is present, and the risk is best treated as a credible mid-tier patch priority rather than a drop-everything emergency; vendor patches are available via the Microsoft Security Response Center advisory.
Local privilege escalation in Microsoft Exchange Server stems from deserialization of untrusted data (CWE-502) that an attacker with an existing, authenticated foothold on the host can trigger through the vulnerable code path. Because the attack vector is local (CVSS AV:L, PR:L, UI:N), this is not remotely reachable on its own - it is realistically a post-compromise escalation step that lets an already-present authorized user raise privileges to the Exchange service context, with high impact to confidentiality, integrity, and availability. No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; vendor patches are available for Exchange Server 2019 CU14, 2016 CU23, and Subscription Edition.
Local privilege escalation in the Windows Health and Optimized Experiences Service on Windows 11 (24H2, 25H2, 26H1, 26H2) allows an authenticated low-privileged attacker to gain elevated privileges by exploiting missing authentication for a critical function (CWE-306). The service runs by default and requires no user interaction, with low attack complexity, but the attacker must already have local access; this is an escalation primitive, not a remote entry vector. No public exploit identified at time of analysis.
Local privilege escalation in the Windows Win32k kernel subsystem allows an attacker who already holds a low-privileged local account on an affected Windows 11 or Windows Server build to trigger an out-of-bounds kernel read that Microsoft rates as elevation of privilege with High confidentiality, integrity, and availability impact. Exploitation requires local authenticated access (AV:L, PR:L) and no user interaction (UI:N), but the High attack complexity (AC:H) indicates success likely depends on winning a race or arranging a specific kernel memory state, so it is not reliably repeatable. There is no public exploit identified at time of analysis, the flaw is not confirmed actively exploited (CISA KEV), and the CVSS 7.8 (High) score reflects severe technical impact rather than an imminent, easily triggered attack.
Local privilege escalation in the Windows Kernel allows an attacker who already holds low-privileged code execution on a Windows 11 version 26H1 host (builds from 10.0.28000.0 up to, but not including, 10.0.28000.3231) to raise their privileges to kernel/SYSTEM level. The defect is a release of an invalid pointer or reference (CWE-763), which under the assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H requires no user interaction and no non-default configuration, so any standard interactive or service account able to run code can attempt it. Successful exploitation yields full loss of confidentiality, integrity, and availability on the host. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited; Microsoft has published a vendor fix through the MSRC update guide, making this a patch-priority item rather than an emergency one, with the mandatory prior local foothold being the primary limiting factor.
Local privilege escalation in Windows Direct Composition - the desktop compositor subsystem shipped by default in Windows 11 24H2, 25H2 and 26H2 and in Windows Server 2025, including Server Core - lets an attacker who already holds low-privilege local access corrupt heap memory and execute code at a higher integrity level (CVSS:3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is bounded by the prerequisite of an existing authenticated foothold on the host, so this is a post-compromise escalation primitive rather than a remote entry point; the independent assessment rates it a credible but not emergency-level priority. A vendor patch is available from Microsoft, and there is no public exploit identified at time of analysis (SSVC exploitation: none) and no KEV listing.
Local privilege escalation in the Windows Program Compatibility Assistant Service (PcaSvc) allows an authenticated, low-privileged attacker who already has code execution on the host to gain SYSTEM-level privileges. The root cause is an improper null-termination defect (CWE-170) in the service, which is present and running by default on affected Windows 11 23H2/24H2/25H2/26H1/26H2 builds and Windows Server 2022/2025 (including Server Core installations); the CVSS vector (AV:L/AC:L/PR:L/UI:N) means no user interaction and low attack complexity, but a prior local foothold and valid low-privileged credentials are prerequisites, making this a post-compromise escalation primitive rather than a remotely reachable flaw. Microsoft has published fixed builds and no public exploit has been identified (SSVC exploitation: none), so this is a credible patching priority rather than an emergency.
Heap-based buffer overflow in the Windows Win32K kernel-mode driver (win32kbase.sys/win32kfull.sys) lets an attacker who already holds a low-privileged local session on a Windows host corrupt kernel pool memory and elevate to SYSTEM-level privileges. The flaw is rated CVSS 7.8 (AV:L/PR:L/UI:N, high confidentiality, integrity and availability impact) and affects Windows 11 23H2 through 26H2, Windows Server 2022, and Windows Server 2025 including Server Core installations below the patched build numbers. Exploitation is not remote and requires pre-existing local access, so it functions as a post-compromise privilege-escalation step rather than an initial-access vector; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing). Microsoft has issued a fix, making this a credible, patch-worthy local privilege-escalation issue rather than an emergency on its own.
Local privilege escalation in Windows Kernel allows an authenticated low-privileged user who can execute code on an affected Windows 11 or Windows Server 2025 host to trigger a release-of-invalid-pointer/reference condition and elevate to higher privileges, with high confidentiality, integrity, and availability impact. The flaw affects default configurations of Windows 11 23H2, 24H2, 25H2, 26H1, and 26H2 as well as Windows Server 2025 and Server Core below their patched builds, and it requires local access rather than remote reachability. Microsoft has released a vendor patch, no public exploit was identified at time of analysis, and CISA SSVC records exploitation as none.
Local privilege escalation in the Windows Win32k kernel-mode driver (win32kfull.sys/win32k.sys) allows an attacker who already holds low-privileged, authenticated code execution on a host to trigger a use-after-free (CWE-416) on a freed kernel object and elevate to a higher-integrity, kernel-level context. Affected deployments are unpatched Windows 11 24H2, 25H2, 26H1 and 26H2 plus Windows Server 2025 (including Server Core) builds below the fixed build numbers published in Microsoft's update guide; CVSS 3.1 score is 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). There is no remote or network attack surface, and no public exploit code and no confirmed active exploitation were identified at time of analysis (CISA SSVC exploitation: none); vendor patches are available.
Local privilege escalation in the Windows Defender Firewall Service lets an authenticated attacker who already holds a low-privileged foothold on a Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2) or Windows Server 2025 host trigger a use-after-free condition and elevate to full SYSTEM privileges, with high impact to confidentiality, integrity, and availability (CVSS 7.8, AV:L/PR:L/UI:N). The vulnerability cannot be reached remotely or by an unauthenticated user, and exploitation is additionally bounded by the affected build ranges, so fully patched systems are not exposed. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the independent assessment rates this as a credible but not emergency-level priority, making it a standard monthly-patch item rather than an out-of-band emergency.
Local privilege escalation in the Windows Resilient File System (ReFS) Deduplication Service allows an attacker who already holds authenticated low-privilege access on an affected host to escalate to a higher-integrity context. Exploitation is only possible where a ReFS volume has the optional Data Deduplication feature installed and the deduplication service is running - a non-default storage configuration typical of file and storage servers rather than standard desktops - and affected builds are limited to Windows Server 2025 below 10.0.26100.33650, Windows 11 23H2/24H2/25H2/26H2 below their respective patched builds, and Windows 11 26H1 below 10.0.28000.3231. Microsoft has released a fix, and there is no public exploit identified at time of analysis; CISA's SSVC assessment rates exploitation as none and automatable as no, so this is a moderate-priority local escalation rather than a broadly exploitable, wormable issue.
A heap-based buffer overflow in the Windows RPC Runtime lets an authenticated local attacker with standard user rights elevate to higher privileges on affected Windows 11 hosts. The flaw is only reachable by code already executing on the machine (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) and the vulnerable component is core, always-present Windows infrastructure, so no special configuration or user interaction is needed once a foothold exists. Microsoft has released fixes in its update guide (MSRC advisory for CVE-2026-83518), and there is no public exploit identified at time of analysis (SSVC exploitation: none, CISA KEV not listed); this makes it a patch-priority item for fleets still running unpatched Windows 11 builds rather than an emergency.
An out-of-bounds write (CWE-787) in Adobe FrameMaker allows an attacker to corrupt memory and potentially execute arbitrary code with the privileges of the user who opens a maliciously crafted document. Affected builds are FrameMaker 2026 at or below 18.0.0.206 and FrameMaker 2022 at or below 17.0.9.866. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8) confirms there is no network or unauthenticated trigger: exploitation depends on social engineering a victim into opening a booby-trapped file, and any code that runs is confined to the current user's rights with no privilege escalation. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, making this a credible but not emergency-tier patching priority.
Unsafe deserialization in NVIDIA Megatron-LM's checkpoint-loading routine allows an attacker to execute arbitrary code, escalate privileges, disclose information, and tamper with data by convincing a user to load a maliciously crafted checkpoint or model file into the framework. The flaw is rated CVSS 7.8 (High) and is reachable only when a victim actually opens an attacker-supplied checkpoint, so organizations that load checkpoints exclusively from trusted internal sources are not realistically exposed; the vulnerable path is local (AV:L) and depends on user interaction per our assessment, with no network service or authentication bypass involved. No public exploit code has been identified at time of analysis and the vulnerability is not in CISA KEV, though the availability of proof-of-concept tooling for pickle-based deserialization attacks in ML frameworks makes this class of issue practically exploitable once a crafted checkpoint is delivered.
Deserialization of untrusted data in the NVIDIA Megatron-LM checkpoint-loading path allows code execution, privilege escalation, information disclosure, and data tampering when a user is convinced to load a maliciously crafted checkpoint file. NVIDIA PSIRT scores this CVSS 7.8 (High) and both the vendor and the independent assessment agree on full confidentiality, integrity, and availability impact; the assessments differ on prerequisites, with the vendor vector indicating low privileges and no user interaction (PR:L/UI:N) while the independent assessment models it as no privileges with required victim interaction (PR:N/UI:R). No public exploit code or CISA KEV entry was identified at time of analysis, and only environments that actually load untrusted checkpoints are exposed; code runs with the privileges of the loading user or process, not inherently as root.
Eval injection in NVIDIA Isaac Lab allows a local attacker who can supply crafted input - such as a malicious experiment configuration, task/environment definition, or command-line parameter - to achieve arbitrary code execution, information disclosure, data tampering, and denial of service once a user opens, loads, or runs the content. The flaw is rated CVSS 7.8 (HIGH) with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H: no privileges are required (PR:N) but the victim must interact with the malicious input (UI:R), the attack path is local (AV:L), and impact is scoped to the invoking user (S:U), so no privilege escalation is implied. The CPE entry is a wildcard with no version boundary and no fixed version is published in the available data, so all Isaac Lab releases should be treated as potentially affected; no public exploit code and no confirmed active exploitation have been identified at time of analysis.
Command approval bypass in Roo Code through 3.54.0 allows unauthenticated remote attackers to execute shell commands that the user or policy has denied, using indirect prompt injection to hide a denied command inside an allowlisted command such as echo. Exploitation is constrained: the host must use bash 5.3+ or ksh93 for the ${ command; } function-substitution syntax to be misread by parseCommandLine(), and Roo Code's auto-approve feature must already permit at least one command that can carry the injected payload. No CISA KEV listing and no public exploit identified at time of analysis; this is a context-dependent moderate-to-high priority issue rather than a mass-exploitation emergency, and it requires user interaction with attacker-controlled content.
Arbitrary file-system write in Adobe Experience Manager 6.5 (through 6.5.25) and AEM 6.5 LTS (through LTS SP3) allows an authenticated low-privileged attacker to place files in unauthorized locations on the host by sending a crafted request that manipulates a pathname and escapes the intended directory. No user interaction is required and attack complexity is low, but the attacker must already hold a valid low-privilege AEM account and be able to reach the instance over the network; the assessed vector (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N) shows a scope change with high integrity impact and no direct confidentiality or availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this is a credentialed post-authentication persistence and integrity risk rather than an opportunistic internet-wide exploit, though it is a credible escalation step for anyone who already has a foothold in AEM.
Siemens Industrial Edge App Publisher versions below V1.27.9 fails to sanitize or escape data received from the backend before rendering it in its integrated Node.js front end, enabling injected JavaScript to execute with the client's privileges and escalate to remote code execution on the victim's machine. Exploitation requires an attacker to control or influence backend-delivered data and a victim to actively view that data in the vulnerable client, making this a targeted threat rather than opportunistic mass exploitation. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has released a patch in V1.27.9.
Command-approval bypass in Roo Code through 3.54.0 lets attacker-influenced input cause the agent to execute arbitrary shell commands without the normal user confirmation prompt. The flaw lives in parseCommandLine(), which validates only the first token of a command against the auto-approval allowlist, so a payload such as $(echo touch /tmp/x) placed in command position passes the echo allowlist check while the shell substitutes and runs the embedded command. Exploitation is unauthenticated in the sense that no Roo Code credentials are required (CVSS 4.0 PR:N), but it depends on attack requirements and passive user interaction (AT:P/UI:P): the victim must run a vulnerable build with command auto-approval enabled and at least one allowlisted command, and must direct the agent at attacker-controlled content (web pages, repository files, issues or dependency docs) that carries an indirect prompt injection. Vendor CVSS 4.0 base is 7.7 (High) with full confidentiality, integrity and availability impact on the local host; no scope change to downstream systems, and no public exploit identified at time of analysis - no confirmed actively exploited (CISA KEV) status was reported. The independent assessment rates the flaw CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, emphasizing that the non-default auto-approval/allowlist configuration and the need for the developer to actively operate the agent on hostile content are the primary constraints on real-world exposure.
Auto-approval command filtering in Roo Code through 3.54.0 can be bypassed, letting an attacker run commands that should have required explicit user approval. The flaw lives in parseCommandLine(), which drops command substitutions written next to '*' or '?' glob tokens, so a payload such as 'echo *$(...)' is checked against the allowlist as though it were only the benign prefix 'echo'. Exploitation is conditionally gated and requires two things to line up: the auto-approval/command-allowlist feature must be enabled, and the attacker must land an indirect prompt injection in content the agent reads (source files, repository data, issues, or web content); version 3.54.0's CVSS 4.0 base score is 7.7 (AV:N/AC:L/AT:P/PR:N/UI:P), and our independent assessment rates it CVSS:3.1/AV:N/AC:H/PR:N/UI:R with high confidentiality, integrity, and availability impact once those conditions are met. No confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, though the referenced public technical writeup documents the bypass pattern in detail.
Command approval bypass in Roo Code through 3.54.0 lets an attacker get denied shell commands auto-approved and executed by the AI coding agent, defeating the allowlist/auto-approve safety control. The flaw lives in parseCommandLine(), where a quote-masking regex can be desynchronized using escaped or single-quoted double quotes so that command separators are hidden behind an allowlisted prefix such as echo; because the agent's auto-approval logic sees only the benign prefix, it runs the trailing command without user confirmation. It is unauthenticated (CVSS PR:N) but requires the victim to have the auto-approve allowlist enabled with permissive prefixes and to run the agent over attacker-controlled content (indirect prompt injection, e.g. a malicious file, repo, issue, or fetched page), so exploitation is conditional rather than remotely triggerable at will; no public exploit code was identified at time of analysis, and the issue is not confirmed actively exploited (CISA KEV). Vendor patch status: no vendor-released patch identified at time of analysis.
SQL injection in Siemens RUGGEDCOM CROSSBOW (all versions prior to V6.0) allows an authenticated user who can create or edit device group or facility names to execute arbitrary SQL commands against the underlying database, with the injected payload only firing when those stored names are subsequently processed by the Bulk Export workflow. Attackers must hold valid credentials with name-editing privileges, and the assessed vectors (CVSS 4.0 base 7.7 with AC:H/PR:L; independent CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) indicate additional non-default preconditions must be satisfied before the payload executes. No public exploit code has been identified at time of analysis, and this is a credentialed, moderate-priority vulnerability rather than a mass-exploitation emergency, with realistic exposure largely limited to insiders or attackers who have already compromised an operator account on an unpatched installation.
Incorrect authorization (CWE-863) in Adobe ColdFusion 2023 through update 2023.0.25 and ColdFusion 2025 through update 2025.0.13 enables a low-privileged authenticated attacker to bypass security measures and gain unauthorized write access over the network without user interaction. This moderate-priority vulnerability has a CVSS 3.1 score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N), reflecting a scope change and high integrity impact. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; Adobe advisory APSB26-144 provides mitigation guidance.
Roo Code through 3.54.0 can execute shell commands that its command auto-approval allowlist is meant to deny, because getCommandDecision() misinterprets a command prefixed with a bare >& redirect and matches the redirect target such as echo instead of the actual denied command. An attacker who can deliver malicious content to the coding agent via indirect prompt injection can bypass the allowlist when a developer runs the agent with auto-approval enabled, gaining full confidentiality, integrity and availability impact on the developer’s machine; exploitation is gated by the need for an indirect prompt injection and active user interaction, and no public exploit was identified at time of analysis. The issue affects versions at or below 3.54.0 and is addressed in versions after 3.54.0, with the supplied CVSS 4.0 vector scoring 7.7 High.
Missing authentication on a command-execution path in Commvault CVFS (the file-system component used in Commvault Cloud and Grid HSX deployments) allows an attacker who already sits on the same network segment as the node to execute commands without supplying credentials or relying on any user action. The attack surface is deliberately narrow: successful exploitation requires adjacent-network reachability (AV:A) plus an additional attack precondition that is outside the attacker's direct control (AT:P), which is why the overall severity lands at 7.7 rather than critical despite high confidentiality, integrity, and availability impact on the affected host. Commvault has published a maintenance release that resolves the condition, and no public exploit code has been identified at the time of analysis; defenders should prioritise network segmentation of backup and storage subnets alongside the upgrade.
Unauthenticated remote attackers can obtain another client's PHP session identifier from FrankenPHP worker mode before 1.12.5 when the session extension is loaded as a shared module rather than statically compiled in. Because frankenphp_reset_session_state() is compiled out under that build configuration, PS(id) persists across request boundaries on the same worker thread, so a later session_start() may keep a stale identifier instead of adopting the new request's cookie, and under concurrent requests session_id() can return a different user's identifier - enabling information disclosure, session hijacking, and intermittent logouts, with integrity and availability also impacted (CVSS 7.7, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L, CWE-362). Exposure is conditional: official static binaries and Docker images that link the session extension statically are not affected, non-worker (classic) mode is not implicated, and the leak is intermittent and timing-dependent; no public exploit code or confirmed active exploitation was identified at time of analysis.
Denial of service in the Windows WLAN Service affects Windows 11 builds 23H2 through 26H2 and Windows Server 2025, where an integer underflow in the wireless networking component can be triggered by an unauthenticated attacker to exhaust or crash the service. Per the assessed CVSS vector (AV:N/AC:L/PR:N/UI:N, C:N/I:N/A:H), no credentials or user interaction are required and the sole impact is loss of availability, with the practical gating factor being reachability of the WLAN stack rather than direct internet exposure; no public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none, and vendor patches are available. CISA's SSVC also flags the issue as Automatable: yes with partial technical impact, making it a moderate-priority patching item for wireless-capable endpoints and servers.
An out-of-bounds read in the Windows Network Policy Server (NPS) role lets unauthenticated remote attackers crash or degrade the service, producing a denial-of-service condition on hosts that expose NPS to the network. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), no credentials, user interaction, or client-side conditions are required once NPS is reachable, and impact is confined to availability - no code execution, integrity, or confidentiality loss. Exploitation is not confirmed active (CISA SSVC reports Exploitation: none) and no public exploit code has been identified at time of analysis, though the flaw is rated Automatable: yes and affects a broad set of Windows client and server builds spanning Windows 10/11 and Windows Server 2012 through 2025; a vendor patch is available and should be prioritized on internet- or partner-facing RADIUS infrastructure.
Denial of service in Windows DNS Server: an unauthenticated, network-reachable attacker can send crafted DNS traffic to a host running the DNS Server role and trigger an out-of-bounds read (CWE-125) that disrupts or crashes the service, scored CVSS 7.5 (AV:N/AC:L/PR:N/UI:N, availability impact only). Unpatched Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025 installations are affected, with Active Directory domain controllers and internet-facing resolvers carrying the greatest exposure because the DNS role must be listening by default; there is no public exploit identified at time of analysis, and CISA's SSVC assessment records exploitation as 'none' with partial technical impact. Microsoft has released fixes through the MSRC update guide, and the impact is confined to service disruption with no code execution or data disclosure resulting.
A memory-leak flaw (CWE-401) in the Microsoft Windows DNS Server service lets an unauthenticated, remote attacker gradually exhaust server memory by sending repeated DNS queries, ultimately degrading or denying DNS resolution on affected hosts. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N with availability-only impact (A:H), no credentials or user interaction are required, and any default DNS-server deployment reachable on the network is exposed; however, this is a slow resource-exhaustion condition rather than an instantaneous crash, so the practical impact scales with sustained traffic and available memory. An independent assessment rates this as a genuine but second-tier priority: SSVC indicates no known exploitation, no publicly available exploit code has been identified at time of analysis, and a vendor patch is available, making timely patching the decisive control.
Denial of service in the Windows DNS Server role allows an unauthenticated remote attacker to take DNS name resolution offline on affected Windows Server hosts by sending a crafted request that drives the service into an unhandled exception. Impact is limited to availability (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) with no confidentiality or integrity loss, and no public exploit was identified at time of analysis (CISA SSVC Exploitation: none, though the bug is rated Automatable: yes). Any Windows Server 2012, 2012 R2, 2016, 2019, 2022 or 2025 system - including Server Core installations - that runs the DNS Server role and is reachable on its DNS listening port is exposed; internal resolvers behind firewalls are materially less at risk than internet-facing ones.
Memory corruption in the Microsoft Windows DHCP Server role allows unauthenticated remote attackers to execute arbitrary code on affected servers over the network. Only systems with the DHCP Server role installed and running are exposed - the attack surface is the DHCP service itself (typically UDP 67), while ordinary Windows clients and servers without that role are not vulnerable. Affected builds span Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025 (including Server Core installations) as well as Windows 10 versions 1607 and 1809 below the listed patch levels. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records no observed exploitation and a non-automatable attack profile, although technical impact is rated total; a vendor patch is available. Note that the vendor-published base vector (7.5) reflects an availability-only impact, whereas the independent assessment scores confidentiality, integrity and availability all High (full code execution).
An out-of-bounds read in the Network Device Enrollment Service (NDES) role of Active Directory Certificate Services allows an unauthenticated remote attacker to crash the SCEP enrollment endpoint on affected Windows servers, producing a denial of service (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Only hosts where the optional NDES role is installed and reachable over the network are exposed, spanning Windows Server 2012 through Windows Server 2025 plus Windows 10 versions 1607 and 1809, and Microsoft has published vendor fixes for these builds. No public exploit code and no confirmed active exploitation were identified at the time of analysis, and real-world exposure is bounded because NDES is a deliberately deployed, non-default role rather than a component present on every Windows server.
Out-of-bounds memory reads in Microsoft's Network Device Enrollment Service (NDES) allow a remote, unauthenticated attacker to disrupt certificate-enrollment service by sending crafted requests to a reachable SCEP endpoint, yielding a denial-of-service condition rated CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Exposure is narrow in practice: NDES is an optional Active Directory Certificate Services role that is not present in a default Windows Server installation, so only hosts where the role has been deployed and its HTTP/HTTPS SCEP interface is network-reachable are at risk, and the vector requires no authentication, privileges, or user interaction. Impact is confined to availability - the assessed vector shows no confidentiality or integrity loss - and no public exploit identified at time of analysis, though vendor patches are available for all affected builds.
Denial of service in Windows Host Guardian Service (HGS) affects servers where the optional HGS role is installed and its network endpoint is reachable. An unauthenticated, remote attacker can trigger a stack-based buffer overflow (CWE-121) to crash or disrupt HGS, impacting attestation and key-protection services for guarded hosts; the CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5). CISA SSVC records exploitation as none and no public exploit code has been identified at time of analysis, and the narrow HGS deployment footprint makes this a bounded, medium-priority patch rather than an emergency.
Denial of service in the Windows Storage Spaces Controller allows remote attackers to crash affected Windows hosts by sending crafted input over the network that triggers a heap-based buffer overflow, with no authentication or user interaction required per the CVSS vector (AV:N/AC:L/PR:N/UI:N). Exploitation is limited to availability impact (C:N/I:N/A:H, CVSS 7.5): the flaw cannot be leveraged for data theft or code execution based on available data. No public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV does not list this CVE); CISA SSVC rates exploitation as "none" while noting the attack is automatable, and a vendor patch is available.
Unauthenticated, network-reachable attackers can deny service on Windows hosts that run the Routing and Remote Access Service (RRAS) by triggering an out-of-bounds read (CWE-125) that crashes or destabilizes the service. Rated CVSS 3.1 7.5 HIGH (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), the impact is availability-only with no confidentiality or integrity effect, and exposure is restricted to systems where the non-default RRAS role is installed and its listener is reachable over the network, requiring no credentials and no user interaction. No public exploit code identified at time of analysis and the issue is not listed in CISA KEV; vendor patches are available.
Denial of service in the Windows Routing and Remote Access Service (RRAS) allows a remote, unauthenticated attacker to crash the service by sending crafted network traffic that triggers a null pointer dereference, taking down routing, VPN, NAT, and dial-up functions on the host. Per the provided vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5), exploitation requires no credentials and no user interaction, and the impact is confined to availability with no confidentiality or integrity effect. The practical limitation is deployment: RRAS is not enabled by default, so only servers configured as VPN gateways, routers, or NAT/dial-up endpoints with a reachable listener are exposed; CISA's SSVC assessment rates exploitation as 'none' and no public exploit has been identified at time of analysis, though the attack is automatable and a vendor patch is available.
Denial of service in the Windows Graphics Device Interface (GDI) subsystem allows unauthenticated, remote attackers to trigger a stack-based buffer overflow (CWE-121) and crash affected components, requiring no user interaction. The flaw (CVSS:3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) affects all supported Windows client and server editions, including Server Core installations, but impact is confined to availability - there is no confidentiality or integrity loss, code execution, or privilege escalation described. CISA's SSVC assessment records exploitation as "none" and notes the flaw is automatable; no public exploit code was identified at time of analysis, and a vendor patch is available per the Microsoft advisory.
An out-of-bounds read in the Windows Internet Key Exchange (IKE) protocol implementation allows an unauthenticated remote attacker to cause a denial of service on affected hosts, with a CVSS base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) reflecting availability-only impact. Windows 10, Windows 11 (23H2 through 26H2), and Windows Server 2012 through 2025 are affected, but exploitation is only reachable on hosts that actually expose an IKE/IPsec listener on UDP 500/4500 to the attacker's network - typically VPN gateways, IKEv2 remote-access servers, or hosts under domain IPsec policy. No public exploit identified at time of analysis, CISA SSVC records exploitation as 'none', and Microsoft has released vendor patches listed in the MSRC update guide.