Authentication Bypass

Unauthenticated file disclosure in Omnispace Agora Project before version 26.10.0 allows any remote attacker who can reach the MobileFileDownload route to retrieve files they are not authorized to access. The route treats md5(filename) as a capability token rather than performing a real access-control check, and because MD5 is deterministic and unsalted, an attacker who guesses or otherwise learns a stored filename can compute a valid token and download the file. No credentials or user interaction are required (CVSS:3.1 AV:N/AC:L/PR:N/UI:N, confidentiality-only impact), CISA's SSVC assessment records exploitation as none observed while noting the attack is automatable with partial technical impact, and no public exploit code has been identified at time of analysis; the practical constraint is how guessable the target filenames are. A vendor patch is available in release 26.10.0.

Session fixation in Omnispace Agora Project before 26.10.0 lets remote, unauthenticated attackers hijack a victim's authenticated session by planting a known session identifier in the victim's browser and waiting for them to log in, because the application does not regenerate the session ID after successful authentication. Exploitation hinges on victim interaction - the target must follow attacker-supplied content that sets a chosen identifier and then actively authenticate to that same session (CVSS UI:A), which is the primary factor limiting real-world abuse. No public exploit code has been identified and the flaw is not confirmed as actively exploited (CISA KEV), and the vendor has shipped 26.10.0 as the fixed release.

Authentication bypass in Omnispace Agora Project before 26.10.0 allows anyone holding a user's stored bcrypt password hash to log in as that user - including administrators - by replaying the hash inside the legacy AGORAP_LOG/AGORAP_PASS cookies, never needing the plaintext password. The flaw maps to CWE-836 (use of a password hash instead of the password) and is scored 9.1 in CVSS 4.0 with PR:N, meaning no application login is required to launch the attack; however, the practical gate is a prerequisite credential disclosure, since the attacker must first obtain a valid hash from the Agora credential store (database compromise, exposed backup, or SQL injection), which is why the AC:H assessment applies. The vendor addressed it in release 26.10.0 (vendor-released patch: 26.10.0); no public exploit code has been identified at time of analysis and no EPSS score was supplied.

Authenticated users of Omnispace Agora Project instances running versions before 26.10.0 can insert access-right records (affectations) for arbitrary spaces by invoking setAffectations() with a caller-supplied target space identifier, breaking tenant isolation and extending access to spaces the caller has no rights over. Exploitation is network-reachable, low-complexity, requires only a valid account on the target instance (CVSS PR:L), and needs no user interaction or non-default configuration, yielding high confidentiality and integrity impact while availability is unaffected. No public exploit code has been identified at time of analysis, but because the flaw is a straightforward authorization-check omission reachable by any logged-in user, multi-tenant or shared-hosting deployments carry the highest realistic risk; the vendor-released fix is Agora Project 26.10.0.

Unauthenticated remote code execution in Adobe Experience Manager stems from an incorrect authorization check that lets a remote attacker bypass access controls and execute arbitrary code in the context of the current user, with the changed-scope rating indicating impact can extend beyond the vulnerable component (CVSS 3.1 base 10.0, AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Every unpatched deployment is in scope: AEM 6.5 up to and including 6.5.25, AEM 6.5 LTS up to and including 6.5 LTS SP3, and AEM as a Cloud Service up to and including 2026.9.28187; no credentials or user interaction are required, and the only practical precondition is that the affected author, publish, or endpoint is reachable from the attacker's network. No public exploit code exists and no confirmed active exploitation (CISA KEV) has been recorded at time of analysis, but the authentication-bypass-to-RCE chain plus the maximum severity score make internet-facing, unpatched instances a top remediation priority rather than a high-score/low-real-risk case.

Unauthenticated remote code execution affects Adobe Experience Manager, specifically AEM as a Cloud Service builds up to and including 2026.9.28187, AEM 6.5 LTS up to and including SP3, and AEM 6.5 up to and including 6.5.25, and is rooted in an incorrect authorization check (CWE-863) that carries a maximum CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Because the defective access-control decision itself is the entry point, a remote attacker needs only network reachability, no credentials, and no user interaction, and the changed scope (S:C) means the resulting arbitrary code execution in the current user's context can be leveraged to gain elevated access or control over a victim's account or session beyond the vulnerable component. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but the unauthenticated, no-interaction exploitation profile places internet-exposed AEM instances at top-priority risk, with network isolation (VPN, WAF, non-exposed tiers) and the affected-version boundaries as the main mitigating factors.

Cross-tenant authorization bypass in Lowcoder (versions 2.1.0 through and including 2.4.10) lets an authenticated administrator or developer from one organization execute a library query that belongs to a different organization by sending a crafted request containing the victim's library-query identifier to the library-query execution endpoint. The flaw yields full confidentiality, integrity, and availability impact against the targeted tenant's query data (CVSS 8.8, PR:L), but only on shared multi-organization deployments where the attacker already holds a privileged account and can determine a valid target identifier. No public exploit code and no CISA KEV activity have been identified at time of analysis, and EPSS is low at 0.16% (5th percentile), so this is a credible but context-dependent priority rather than a mass-exploitation threat.

Blind XPath/XML injection in Adobe Experience Manager 6.5 (versions 6.5.0 through 6.5.25) allows a low-privileged, authenticated attacker to bypass security controls and read content they should not be able to access, with limited unauthorized write capability. The flaw is network-reachable, requires no user interaction, and carries a CVSS 3.1 base score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N), reflecting high confidentiality impact but only low integrity impact and no availability impact; the CVSS vector confirms the attacker must hold a valid low-privileged account (PR:L), so unauthenticated outsiders cannot exploit it directly. No public exploit code or confirmed active exploitation was identified at time of analysis, and Adobe has published a vendor security bulletin (apsb26-152) covering the issue.

Remote code execution in Visual Studio Code versions 1.0.0 through 1.141.1 allows an unauthenticated, network-positioned attacker to execute arbitrary code when a victim opens attacker-controlled content (e.g., a crafted workspace, folder, or repository), due to improper output encoding/escaping (CWE-116). Exploitation requires user interaction, and no public exploit code has been identified at time of analysis. The vendor has released a patch in version 1.141.1.

An unauthenticated, network-positioned attacker can bypass a security feature in Visual Studio Code versions 1.0.0 up to but not including 1.141.1 by getting a victim to open or interact with attacker-controlled content, resulting in high confidentiality impact (CVSS 7.4, S:C/C:H/I:N/A:N). The user-interaction requirement (UI:R) is the primary limiting factor - the flaw cannot be triggered fully passively and no privileges or local access are needed once the victim interacts. Neither KEV confirmation nor public exploit code has been identified at time of analysis, so this is a moderate-priority patching item rather than an emergency, though the scope-changed, high-confidentiality rating keeps it above routine maintenance.

Improper type validation in Microsoft .NET Framework allows unauthenticated remote attackers to tamper with data in .NET-based applications that parse attacker-supplied input over the network, affecting multiple framework branches including 3.5, 4.6.2 through 4.8.1. Microsoft has released patched builds for each affected branch (for example, 4.8.4811.0 for .NET Framework 4.8 and 4.8.9363.0 for 4.8.1), so exploitation is only possible against unpatched systems; no public exploit code or active exploitation is identified at time of analysis. The CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) reflects a network-reachable flaw whose impact is confined to integrity tampering, with no confidentiality or availability effect.

Local privilege escalation in the Windows Setup and Deployment component allows an attacker who already holds a low-privileged authenticated session on the host to invoke a critical setup/deployment function that performs no authentication check, resulting in full compromise of confidentiality, integrity, and availability of the affected system. The flaw is not remotely reachable: it requires local access (AV:L), a pre-existing low-privileged account (PR:L), and the high attack complexity (AC:H) reflects an additional precondition such as a timing or state dependency during setup or deployment, so exploitation is a post-compromise escalation step rather than an initial-access or mass-exploitable vector. Affected platforms include Windows 11 (23H2 through 26H2/26H1), Windows 10 (1809, 21H2, 22H2), and Windows Server 2019, 2022, and 2025 including Server Core, and a vendor patch is available per the Microsoft MSRC advisory; no public exploit code has been identified at time of analysis, and no CISA KEV listing is associated with this CVE.

Remote code execution in Microsoft Excel is possible when a user opens a specially crafted spreadsheet, because an integer underflow (CWE-191) in Office's document handling wraps a value and leads to memory corruption exploitable for code execution in the context of the opening user. No authentication is required on the target (PR:N) and the file can be delivered over the network via email, a link, or a shared document, but exploitation depends on the victim opening the file (UI:R), and no server-side or zero-click path is indicated. Microsoft has released fixed builds (for example Office LTSC 2021 16.0.14334.20974 and Office LTSC 2024 16.0.17932.21056), and no public exploit identified at time of analysis; treat this as a high-priority, patch-worthy issue rather than an emergency given the absence of exploitation signals.

Authentication bypass in Microsoft .NET allows an unauthenticated, remote attacker to forge a cryptographic signature and have it accepted by applications that rely on the framework's signature-verification routines, potentially leading to unauthorized access or token misuse. The JWT Attack tag points to a token-signature validation weakness; exploitation requires the target application or user to process the attacker-supplied signed token (UI:R), which limits reachability for purely passive endpoints. Affected versions include .NET 10.0 before 10.0.402, .NET 11.0 before 11.0.100-rc.2, and the listed Visual Studio 2022 17.14.x/2026 18.10.x builds; vendor patches are available, and no public exploit identified at time of analysis.

Privilege escalation in the Windows NTFS filesystem driver allows an authenticated local attacker holding only standard-user rights to reliably obtain SYSTEM-level access on unpatched builds. The weakness is an improper access control condition (CWE-863) that requires low attack complexity and no user interaction, making it a dependable post-foothold escalation step once an attacker already has local code execution - for example via phishing, an existing low-privileged account, or a chained remote bug - rather than a remotely reachable or unauthenticated issue. No public exploit code has been identified and CISA's SSVC assessment records no observed exploitation, so this is a genuine but second-tier patching priority; Microsoft has shipped fixes for all listed client and server editions, so exposure is limited to hosts still below the fixed build numbers.

Unauthenticated remote code execution in the Microsoft Failover Cluster Virtual Driver affects Windows Server 2012 through Windows Server 2025 and Windows 10 1607/1809 installations that have the Failover Clustering role enabled, where a double free (CWE-415) during processing of cluster network traffic allows an attacker to corrupt kernel memory and run code with SYSTEM privileges (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). Exposure is conditional rather than universal: the vulnerable driver is only loaded and reachable on clustered nodes, and in well-architected deployments the cluster communication path sits on a dedicated, isolated interconnect, which materially limits remote reach despite the network vector. There is no public exploit identified at time of analysis and no CISA KEV entry, but the vulnerability is fully automatable (SSVC: Exploitation none, Automatable yes, Technical Impact total) and vendor patches are available for all affected builds.

Local privilege escalation in the Windows Push Notifications service allows an authenticated attacker with low-level user privileges to achieve high-integrity code execution by exploiting a missing authentication check (CWE-306) in a critical internal function. Scored CVSS 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), exploitation requires local access, no user interaction, and winning a non-deterministic condition due to high attack complexity; there is no public exploit identified at time of analysis. Affected builds of Windows 10, Windows 11, and Windows Server (2019 through 2025) below the fixed versions can be remediated with the Microsoft update.

Spoofing in Microsoft Active Directory Federation Services (AD FS) lets a remote, unauthenticated attacker forge signed tokens that the service accepts as legitimate, yielding full compromise of confidentiality and integrity (CVSS 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). The flaw is an improper verification of cryptographic signatures (CWE-347) in the AD FS token-validation path, tagged as an authentication bypass/JWT attack, so a crafted SAML/JWT assertion can impersonate any user or relying party - effectively bypassing federation authentication. Only hosts running the AD FS role on unpatched Windows Server builds (2012 through 2025) are exposed; organizations that do not deploy AD FS are not affected. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA SSVC: Exploitation = none, Automatable = yes, Technical Impact = total), but the vulnerability is considered high-priority because exploitation is trivially automatable and impact is total where the role is exposed.

Unauthorized code execution in Microsoft PowerShell 7.4.x, 7.5.x, and 7.6.x is achievable by remote attackers who get a user to run, import, or otherwise process attacker-controlled PowerShell content, because the product relies on untrusted input when making a security decision (CWE-807). CVSS 3.1 rates this 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H): network-reachable and unauthenticated in vector terms, but gated by a mandatory user-interaction prerequisite, so this is not a drive-by or unattended attack. SSVC records Exploitation:none and Automatable:no, and no public exploit identified at time of analysis; with Technical Impact:total, a successful trigger yields high confidentiality, integrity, and availability impact, but scope is limited to PowerShell 7.4.0 through 7.4.20, 7.5.0 through 7.5.11, and 7.6.0 through 7.6.6.

Code execution in .NET and Visual Studio can be triggered when a developer or user processes attacker-supplied content - such as a crafted project, build input, or dependency - that pulls functionality in from an untrusted control sphere and executes it. Affected builds are .NET 8.0 before 8.0.132, .NET 9.0 before 9.0.319, .NET 10.0 before 10.0.113, Visual Studio 2022 17.14 before 17.14.42, and Visual Studio 2026 18.10 before 18.10.4; the issue is network-reachable and unauthenticated (PR:N) but requires user interaction (UI:R) and non-trivial preconditions (AC:H), so an attacker cannot silently trigger it remotely. There is no public exploit identified at time of analysis and no confirmed active exploitation - the CISA SSVC exploitation value is 'none' - which keeps this a moderate-priority issue rather than a drop-everything emergency despite the 7.5 High CVSS score, especially since the SSVC technical impact is assessed as 'total' once exploitation conditions are met.

Spoofing and identity impersonation in Microsoft Active Directory Federation Services (AD FS) let an unauthenticated network attacker get forged or intercepted certificates accepted as trusted, undermining the integrity of federated authentication. Affected deployments are AD FS running on Windows Server 2012 R2 through Windows Server 2025, along with the underlying .NET Framework certificate-validation components (3.5, 4.6.2 through 4.8.1) and System.Security.Cryptography.Xml, plus Visual Studio 2022 17.14 and Visual Studio 2026 18.10. The assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (7.4), meaning no credentials or user interaction are needed but the attacker must first obtain a privileged network/intercept position or craft a certificate that slips past validation; impact is limited to confidentiality and integrity, with no availability effect. No public exploit code has been identified at time of analysis and CISA KEV does not list this issue, but a vendor patch is available and should be applied promptly given the authentication-bypass potential in default, network-exposed AD FS deployments.

A security-feature bypass in Microsoft Word allows an attacker-crafted document to subvert an Office security decision when the file is opened on the local machine, rated CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) with high confidentiality, integrity, and availability impact. No privileges or authentication are required, but the attacker depends entirely on convincing the victim to open the malicious document, so delivery is social-engineering based rather than unattended. This is tracked as CWE-807 (reliance on untrusted inputs in a security decision) and EUVD-2026-100189; no public exploit identified at time of analysis, and Microsoft has published a fix (patch available per vendor advisory).

Privilege elevation in Microsoft SharePoint Server Subscription Edition lets any attacker who already holds a valid low-privilege account escalate to higher privileges over the network, because a SharePoint function performs an action without the required authorization check. Affected deployments are Subscription Edition builds below 16.0.20326.20190; patched builds are not exploitable. This is a credible mid-tier priority rather than a drop-everything emergency: exploitation requires an authenticated foothold (CVSS PR:L, so authentication requirements are confirmed as authenticated per vector PR:L), no user interaction is needed (UI:N), and CISA's SSVC assessment records exploitation as none and the flaw as not automatable, so no public exploit was identified at time of analysis and the barrier to mass exploitation is high. A vendor patch is available from Microsoft.

Remote code execution in Windows Deployment Services (WDS) on affected Windows Server and Windows 10 systems allows an unauthenticated, remote attacker to exploit a race condition (CWE-362) in shared resource synchronization to execute arbitrary code, but the high attack complexity (AC:H) and lack of automation make reliable exploitation difficult. WDS is an optional role not enabled by default, so only servers actively using WDS for network imaging are exposed. No public exploit code or active exploitation has been reported (SSVC exploitation: none), and the vulnerability is not automatable per CISA SSVC. The assessed CVSS score is 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating total technical impact if successfully exploited. The 'Authentication Bypass' tag suggests the race may also bypass authentication, but the primary effect is network code execution.

Improper access control in the WebDAV component of Microsoft Windows lets a locally authenticated low-privilege user elevate privileges to full system integrity, giving complete compromise of confidentiality, integrity, and availability on the affected host. Exploitation is strictly local (AV:L) with a valid low-privileged account and no user interaction (PR:L, UI:N); there is no remote or network vector, and the attacker must already hold a foothold on the machine, which caps real-world risk. Microsoft has released a vendor patch, no public exploit code has been identified, and CISA's SSVC assessment records exploitation as "none" and automatable as "no", so this is a genuine but not emergency-level priority. Affected builds are all Windows client and server releases below the fixed build numbers catalogued in EUVD-2026-100091, and hosts that have the WebClient/WebDAV service disabled have a materially reduced attack surface.

Request smuggling in the ASP.NET Core Kestrel HTTP/1 server lets a remote, unauthenticated attacker desynchronize HTTP request parsing and tamper with how requests are interpreted by the server and any shared front-end proxy, load balancer, or connection pool. The flaw is triggered when a Kestrel HTTP/1 connection carrying unread request-body bytes is aborted and Kestrel reparses that leftover data as a new request; the vendor rates it Critical at CVSS 9.4 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L), while the independent assessment applies the same impact but rates attack complexity as High because the abort/timing prerequisite must be met, and the practical blast radius is greatest where connections are reused across tenants. Affected runtimes are ASP.NET Core 8.0 before 8.0.32, 9.0 before 9.0.21, 10.0 before 10.0.13, and 11.0 before 11.0.0-rc.2, plus Microsoft Visual Studio 2022 17.14 before 17.14.42 and Visual Studio 2026 18.10 before 18.10.4; a vendor patch is available and there is no public exploit identified at time of analysis.

Hyper-V on affected Windows and Windows Server hosts fails to properly verify the source of a communication channel, letting an unauthenticated attacker on an adjacent network bypass a Hyper-V security feature. The assessed vector (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) indicates high confidentiality impact that crosses a security scope boundary, but with no integrity or availability impact; the practical prerequisite is that the attacker already occupies a position on the adjacent layer-2 / virtual-switch segment, such as a co-resident guest VM or a host on the same segment, rather than reaching the target from the internet. No public exploit code has been identified at time of analysis, CISA SSVC rates exploitation as 'none' and automatable as 'no' (the adjacency requirement prevents trivial mass exploitation), and vendor patches are available. This is a moderate-priority hardening issue rather than an emergency, but it is worth treating seriously in multi-tenant or high-density virtualization environments where untrusted guests may share a virtual switch with sensitive workloads.

Weak authentication handling in Microsoft's Azure Key Vault integration libraries allows unauthenticated remote attackers to bypass a security feature, with high confidentiality and integrity impact but no availability impact. The exposure is limited to applications and services that depend on specific vulnerable client SDK versions - the Python packages azure-keyvault-administration (<4.7.1), azure-keyvault-securitydomain (<1.0.0b3), and azure-keyvault-certificates/secrets/keys (<4.11.2), plus the .NET packages Azure.Security.KeyVault.Certificates/Secrets/Keys (<1.0.1); deployments already on patched versions are not exposed. Although the CVSS 3.1 vector (7.4, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) indicates no authentication or user interaction is required, the High Attack Complexity reflects a meaningful non-trivial precondition - a timing or race window, a specific configuration, or an intermediary network position - rather than a single-request exploit of a default setup; no public exploit code has been identified at time of analysis, and this is a moderate-priority issue rather than an urgent fire drill.

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.

Improper verification of cryptographic signatures in Microsoft Windows Schannel, the operating system's native TLS/SSL provider, allows an unauthenticated attacker who already holds a man-in-the-middle position to spoof a trusted TLS peer and bypass authentication during a handshake. Affected builds include Windows Server 2025 before 10.0.26100.33650, Windows Server 2025 Server Core before the same build, Windows Server 2022 before 10.0.20348.5761, and Windows 11 23H2, 24H2, 25H2, 26H1 and 26H2 below their respective patched build levels. The 9.0 base score reflects high confidentiality and integrity impact with changed scope, but exploitation carries a high-complexity prerequisite (CVSS AC:H) because the attacker must control or inject into the path between the Windows endpoint and its peer; no attacks require credentials (PR:N) and no user interaction is needed (UI:N). No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing), but vendor patches are available and the affected footprint is broad, so remediation should be treated as high priority.

Unauthorized remote code execution in Microsoft Windows PowerShell (CVE-2026-85817) stems from the engine relying on attacker-influenced data when making a security decision (CWE-807), allowing an unauthenticated network attacker to bypass that check and execute code in the context of the affected user. Exploitation requires user interaction (UI:R per the CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H vector) - typically the victim running an attacker-supplied script or module, or opening content that PowerShell evaluates while deciding whether to trust it - so unattended server-side compromise is not indicated. Microsoft has shipped fixes in its update guide, and no public exploit code or confirmed active exploitation was identified at time of analysis; the 8.8 base score reflects full confidentiality, integrity, and availability impact once the required user action occurs.

Unauthenticated remote code execution in the Windows Routing and Remote Access Service (RRAS) allows a network attacker to run arbitrary code in the context of the RRAS service on any host where the RRAS role is installed and its listener is reachable, yielding full compromise of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-122 heap overflow, with an authentication-bypass component implied by the pre-auth reachability of the flaw). Exposure is severely gated by configuration rather than by exploit difficulty: RRAS is not enabled by default on Windows, so only machines acting as VPN, dial-up or routing gateways - across Windows 10/11 and Windows Server 2012 through 2025 builds older than the patched build numbers - are realistically at risk. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none alongside Automatable: yes and Technical Impact: total, and Microsoft has released fixes, so this should be treated as a high-priority patch item rather than an active emergency.

Remote code execution in the Windows Routing and Remote Access Service (RRAS) affects Windows 10 and Windows 11 builds from 1607 through 26H1/26H2 as well as Windows Server 2012 through 2025, including Server Core installations, but only on hosts where the RRAS role is actually installed and enabled. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) indicates an unauthenticated, remotely reachable attacker who requires neither credentials nor user interaction can corrupt memory in the service and gain full impact to confidentiality, integrity, and availability. Because RRAS is not a default role, exposure is limited to systems deployed as VPN, dial-up, NAT, or LAN/WAN routing gateways; a vendor patch is available and no public exploit identified at time of analysis.

Remote code execution in Microsoft's Windows Routing and Remote Access Service (RRAS) lets a remote, unauthenticated attacker corrupt heap memory and execute code on affected hosts, though exploitation requires the victim to perform an action (UI:R) such as initiating or accepting a connection to attacker-controlled remote-access traffic. The Routing and Remote Access Service is an optional Windows role that is not installed by default, which sharply limits the exposed population to systems explicitly configured as VPN or dial-up servers. No public exploit code has been identified at time of analysis and the CISA SSVC assessment records exploitation as 'none'; Microsoft has released fixes, and all Windows 10/11 and Windows Server 2012 through 2025 builds below the fixed revisions listed by EUVD are affected.

An out-of-bounds write in the Windows Local Security Authority Subsystem Service (LSASS) allows a network-positioned attacker to corrupt memory in a high-privilege system process and execute arbitrary code, with the CVSS vector (AV:N/AC:L/PR:L/UI:N) indicating a low-privilege authenticated attacker, no user interaction, and full confidentiality, integrity, and availability impact. The affected surface spans essentially the entire supported Windows fleet, from Windows Server 2012/2012 R2 and Windows 10 1607 through Windows 11 26H2 and Windows Server 2025, so unpatched domain controllers and member servers are the highest-value targets. No public exploit code has been identified at time of analysis and CISA's SSVC assessment records exploitation as none and the flaw as non-automatable, meaning exploitation is not trivial to script at scale; Microsoft has released fixed builds for all affected branches.

Improper privilege management in Windows' WinINet component (wininet.dll) lets an authenticated, low-privileged local attacker spoof a trusted identity and bypass authentication, with the impact spilling beyond WinINet's own security boundary into other components on the host. The flaw is rated CVSS 3.1 8.4 (High) under the vector AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, so an attacker must already hold a local foothold on an unpatched machine, but then needs no user interaction and faces low complexity; CISA's SSVC assessment records exploitation as none, automatability as no, and technical impact as total. Affected platforms are Windows 10 21H2/22H2, Windows 11 23H2 through 26H2 plus 26H1, and Windows Server 2022/2025 builds below the patch thresholds in EUVD-2026-100013; no public exploit code was identified at time of analysis, and Microsoft has released vendor fixes.

Local privilege escalation in the Windows Device Install Service lets an authenticated attacker holding only low-level privileges on a host raise their rights to a higher integrity level (CVSS 3.1 base 7.8 High, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is an incorrect authorization check (CWE-863) in a service that normally runs with high privileges, so any standard user who can already execute code - or plug in or trigger a device installation - on an unpatched Windows 10, Windows 11, Windows Server 2022, or Windows Server 2025 system is a potential victim; default configurations are affected and no user interaction is needed. Microsoft has published a fix, and there is no public exploit identified at time of analysis and no CISA KEV listing or SSVC exploitation signal, though the SSVC technical impact rating is "total" because successful exploitation yields high confidentiality, integrity, and availability impact within the same security scope.

Local tampering and information compromise in Microsoft Windows Error Reporting (WER) allow an authenticated attacker who already holds a low-privileged account and code execution on a Windows host to invoke a critical WER function that performs no authentication or authorization check, yielding high confidentiality and integrity impact with no availability impact (CVSS 7.1, AV:L/PR:L/UI:N). The flaw is not reachable remotely or by unauthenticated users; the mandatory local foothold narrows realistic exploitation to local attackers or post-compromise privilege escalation, which is why the consolidation of signals points to a moderate rather than emergency priority. No public exploit code or confirmed active exploitation has been identified at time of analysis, and Microsoft has released fixed builds covering Windows 10, Windows 11 (23H2 through 26H2), and Windows Server 2012 through 2025.

Authentication spoofing in Microsoft Active Directory Federation Services (AD FS) allows an unauthenticated remote attacker to impersonate or spoof identities through the federation service on affected, unpatched Windows builds, yielding high confidentiality, integrity, and availability impact (CVSS 8.1, AV:N/PR:N/UI:N, C:H/I:H/A:H). Only systems that run the AD FS role on Windows Server 2016, 2019, 2022, or 2025 (including Server Core installations) and the corresponding Windows 10 1607/1809 identity builds are exposed, and the service endpoint must be reachable over the network. The high attack-complexity rating and the CISA SSVC assessment (Exploitation: none, Automatable: no) indicate that reliable exploitation depends on specific, hard-to-control preconditions; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not listed in CISA KEV).

Local privilege escalation in Microsoft Windows Modern Device Management (MDM) stems from a critical function that performs no authorization check (CWE-306), letting an attacker who already holds a low-privilege authenticated local account on the host elevate to higher privileges, including SYSTEM. Affected platforms span Windows 10 21H2/22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2022/2025 (including Server Core) below their respective fixed builds. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) confines this to post-compromise escalation - there is no remote network attack path and no user interaction required - and no public exploit code was identified at time of analysis, with CISA SSVC recording exploitation as 'none' and automatable as 'no'.

Type confusion in the Windows DNS Server role enables unauthenticated remote attackers to execute arbitrary code on affected systems, but exploitation requires user interaction (UI:R) - the DNS server must be induced to process a maliciously crafted record or response. Affected builds include Windows Server 2012 through Server 2025 and Windows 10/11 client installations prior to the patched build numbers listed in Microsoft’s advisory. Microsoft has released patches, and no public exploit or active exploitation has been identified at the time of analysis (SSVC exploitation: none).

Local privilege escalation in the Windows Geotag Broker component of Microsoft Windows lets an authenticated low-privileged user already running code on a host elevate to a higher-integrity context, with the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) indicating high impact to confidentiality, integrity and availability and no user interaction required. Affected systems are unpatched Windows 10, Windows 11 and Windows Server builds below the fixed build numbers published by the vendor, including Server Core installations; exploitation requires local interactive or code-execution access (PR:L, AV:L), so risk is concentrated on multi-user hosts such as RDP/terminal servers, shared workstations and systems where untrusted users can run code. There is no public exploit identified at time of analysis and no CISA KEV listing, and Microsoft has released a vendor patch - this is a patch-priority issue rather than a remotely exploitable emergency.

Spoofing and authentication bypass in the Microsoft Windows IKE Extension allow an unauthenticated remote attacker to subvert a security decision made during Internet Key Exchange negotiation, yielding high confidentiality, integrity, and availability impact (CVSS 3.1 base 8.1). All supported Windows client and server branches that carry the IKE Extension are affected, including Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), and Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025, with Server Core installations included. Exploitation is conditional rather than trivial: the CVSS vector is AV:N/AC:H/PR:N/UI:N, so no credentials or user interaction are required, but the target host must actually have IKE/IPsec configured and actively negotiating and the attacker must hold a network position capable of influencing the handshake (a man-in-the-middle vantage or race-window dependency). CISA's SSVC assessment rates Exploitation as none and Automatable as no while assigning total technical impact, and no public exploit code or in-the-wild activity has been identified - no public exploit identified at time of analysis. Vendor patches are published by Microsoft (EUVD-2026-99912 / CVE-2026-83522) and should be treated as a priority for any estate that runs IPsec.

Spoofing of federated identities in Microsoft Active Directory Federation Services (AD FS) lets an unauthenticated network attacker impersonate a federated user by exploiting weak authentication logic (CWE-1390), with high confidentiality and integrity impact but no availability impact (CVSS 7.4). Exploitation requires a deployed AD FS role reachable over the network and is rated high complexity (AC:H) - CISA SSVC records no known exploitation and rates the flaw as not automatable, and no public exploit code has been identified at time of analysis. Organizations that do not run the AD FS server role are not exposed, and Microsoft has released vendor patches for the affected Windows Server builds and the corresponding Windows 10 client builds.

Privilege escalation in Microsoft Exchange Server allows an attacker who already holds valid low-privilege authenticated access to the environment to perform operations well beyond their assigned permissions, achieving high impact to confidentiality, integrity, and availability (CVSS 8.8, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The root cause is an incorrect authorization check (CWE-863): the server fails to properly validate whether the caller is entitled to the action being performed, so an 'authorized attacker' - a legitimate but under-privileged account - can elevate privileges over the network without any user interaction. Affected builds are Exchange Server 2016 CU23 before 15.01.2507.077, Exchange Server 2019 CU14 before 15.02.1544.050, Exchange Server 2019 CU15 before 15.02.1748.055, and Exchange Server Subscription Edition RTM before 15.02.2562.056; no public exploit code identified at time of analysis, CISA KEV does not list it, and SSVC records Exploitation as 'none' with Automatable 'no', so the practical gate is the need for a pre-existing authenticated foothold rather than remote unauthenticated mass exploitation. This is a genuinely high-priority vulnerability that warrants prompt patching, though the signals are mixed on urgency.

Windows Credential Guard does not enforce authentication on a critical function, letting a local, already-authenticated low-privileged user on an affected Windows host perform spoofing (CVSS 7.8, CWE-306). Exploitation is strictly local and requires prior account access to the machine, so exposure is concentrated on multi-user, shared, or already-compromised endpoints running Credential Guard rather than internet-facing systems; the specific function or configuration state involved is not described in the available sources. Microsoft has released fixed builds for Windows 10, Windows 11 and Windows Server, and no public exploit or CISA KEV entry is associated with the CVE at time of analysis; EPSS is 0.30% (22nd percentile), consistent with a moderate, this-week priority rather than emergency response.

Local privilege escalation in the Windows Bind Filter Driver (bindflt) allows an authenticated, low-privileged user on Windows 11 Version 23H2 and Windows Server 2025 (including Server Core) to gain full control of the affected host, including the ability to read and modify protected data and execute code at kernel/SYSTEM level. The flaw is an improper access control weakness (CWE-863) in a driver that is present by default, requiring only that the attacker already hold a local session on the machine; no user interaction is needed and the scope is changed because escaping the sandbox of a normal user account compromises the entire OS. Microsoft has released fixes, and there is no public exploit identified at time of analysis; CISA's SSVC assessment rates the issue non-automatable, so it is a credible, high-priority local escalation risk rather than an opportunistic mass-exploitation threat.

Privilege escalation in Microsoft SharePoint Server Subscription Edition before build 16.0.20326.20190 allows a remote low-privilege authenticated attacker to abuse an incorrect authorization check and gain elevated privileges. The flaw is network-reachable with low complexity and no user interaction, and it can result in high confidentiality, integrity, and availability impact (CVSS 8.8, PR:L). No public exploit was identified at time of analysis and CISA SSVC records exploitation as none and automatable as no; the vendor patch is available, and patched builds are not exploitable.

Remote code execution against domain controllers running Active Directory Domain Services is achievable by an unauthenticated network attacker (CVSS 3.1: AV:N/PR:N/UI:N) who successfully bypasses an incorrect authorization check, yielding full confidentiality, integrity, and availability impact for a base score of 8.1. The practical constraint is the High attack-complexity rating: exploiting the flawed authorization decision requires an attacker-influenced condition such as a timing window, race, or particular directory state rather than a single deterministic request against a default configuration, and only hosts serving the AD DS role - not member servers or ordinary clients - are the realistic target. At time of analysis no public exploit identified and no confirmed active exploitation (no CISA KEV listing); vendor patch available, with EUVD-listed fixed build levels published.

Local privilege escalation in the Windows StateRepository API allows an authenticated, low-privileged attacker who already has code execution on a Windows 11 host to gain SYSTEM-level rights, because the API's access controls lack sufficient granularity to separate callers by privilege. Affected builds are Windows 11 24H2 below 10.0.26100.9711, 25H2 below 10.0.26200.9711, 26H1 below 10.0.28000.3231, and 26H2 below 10.0.26300.9711. The flaw is not remotely reachable (AV:L, PR:L, UI:N) and CISA's SSVC framework rates it non-automatable with exploitation observed as none, so it functions as a post-compromise escalation step rather than an initial-access vector; no public exploit identified at time of analysis, and a vendor patch is available.

HTTP request smuggling in ASP.NET Core's Kestrel web server allows unauthenticated remote attackers to desynchronize request parsing and bypass security features by having Kestrel accept newline characters in HTTP/2 request trailers and in values drawn from the dynamic HPACK table rather than rejecting them as malformed. All supported ASP.NET Core release trains are exposed - 8.0 before 8.0.32, 9.0 before 9.0.21, 10.0 before 10.0.13, and 11.0 before 11.0.0-rc.2 - along with bundled Visual Studio 2022 17.14 (<17.14.42) and Visual Studio 2026 18.10 (<18.10.4); realistic impact is highest where a proxy, load balancer, or chained server sits in front of Kestrel and performs its own HTTP/2 parsing. The flaw carries a critical CVSS of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) and is rated with total technical impact under CISA SSVC, but exploitation has not been observed (SSVC Exploitation: none) and no public exploit code has been identified at time of analysis.

Windows PowerShell on supported Windows client and server editions fails to enforce a protection mechanism, letting a locally authenticated low-privileged attacker bypass a security feature and operate outside the intended security boundary, achieving high confidentiality, integrity, and availability impact (CVSS 8.8, scope-changed). Exploitation requires a pre-existing local foothold and the ability to run PowerShell on the host - there is no remote or unauthenticated path, and CISA's SSVC assessment rates exploitation as 'none' with Automatable=no, meaning the issue is not wormable or easily mass-scanned. There is no public exploit identified at time of analysis, though the technical impact is rated total once the prerequisite access is obtained; Microsoft has released fixes and the MSRC update guide is the authoritative remediation source.

Authentication bypass by spoofing in the Microsoft.AspNetCore.Authentication.Negotiate package for ASP.NET Core lets an authenticated remote attacker (PR:L) have their Kerberos-authenticated identity associated with an unintended LDAP principal, yielding high confidentiality, integrity, and availability impact (CVSS 7.5) after the attacker reaches the application over the network. Exposure is conditional: the application must use an affected package version - 8.0.0 through 8.0.31, 9.0.0 through 9.0.20, or 10.0.0 through 10.0.12 - and must have LDAP claim resolution enabled, an opt-in and non-default configuration, on Windows, Linux, or macOS. CISA's SSVC assessment records no exploitation, and no public exploit code was identified at time of analysis; the AC:H metric reflects that a specific spoofing/timing condition outside the attacker's full control must be satisfied, making this a genuine but conditional privilege-escalation issue rather than a mass-exploitation emergency.

Account takeover is possible in applications built on ASP.NET Core Identity because the framework's password-reset and email-confirmation flows can dispatch mail to the unvalidated address supplied in the incoming request rather than the user's stored canonical address, allowing a remote unauthenticated attacker who can influence that request address to intercept recovery tokens and reset victim credentials. The issue affects Microsoft.AspNetCore.Identity and Microsoft.AspNetCore.Identity.UI deployments running on ASP.NET Core 8.0 before 8.0.32, 9.0 before 9.0.21, and 10.0 before 10.0.13, as well as certain Visual Studio 2022 and Visual Studio 2026 builds that bundle the affected runtime; it carries a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) under CWE-640. No public exploit code was identified at time of analysis and CISA's SSVC assessment records Exploitation: none with Automatable: no, so this should be treated as a high-priority patching item rather than an active-exploitation emergency.

Remote code execution in the Windows Presentation Foundation (WPF) component of Microsoft .NET and .NET Framework allows an unauthorized remote attacker to run arbitrary code after a victim interacts with a crafted XPS document. The flaw is an improperly implemented security check for URI handling (CWE-358): WPF's XPS hyperlink navigation can bypass its URI restrictions and reach an attacker-controlled ObjectDataProvider, resulting in code execution in the context of the hosting application. Affected runtimes include .NET 8 before 8.0.32, .NET 9 before 9.0.21, .NET 10 before 10.0.13, .NET 11 before 11.0.0-rc.2, multiple .NET Framework 3.5/4.6.2/4.7.x/4.8/4.8.1 builds, and Visual Studio 2022 17.14 before 17.14.42 and Visual Studio 2026 18.10 before 18.10.4; vendor patches are available and there is no public exploit identified at time of analysis, with exploitation gated by mandatory user interaction (UI:R) and SSVC Automatable set to no.

Elevation of privilege in the Microsoft Windows Kernel lets an unauthenticated, remote attacker who can reach the affected kernel code path corrupt or redirect kernel memory and gain SYSTEM-level control of the target host. All currently supported Windows client and server families are in scope - Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025, including Server Core installations - and the assessment vector (AV:N/AC:H/PR:N/UI:N, C:H/I:H/A:H, base 8.1) confirms no credentials or user interaction are needed. The decisive limitation is attack complexity: the attacker must control or influence an untrusted pointer and win a precise kernel memory-layout or timing condition, so this is not a single-shot request. Microsoft has published a fix and there is confirmed vendor patch availability, but no CISA KEV listing and no public exploit code identified at time of analysis; the practical verdict is a genuine high-priority patching candidate rather than a drop-everything emergency.

Local privilege escalation in the Windows AppX Deployment Extensions component allows an authenticated, low-privileged attacker who already has code execution or interactive access on a host to elevate to a higher-integrity context, including SYSTEM, because a required authorization check is missing (CWE-862). The flaw carries a CVSS 3.1 base score of 8.8 from the vector AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - the Scope:Changed rating reflects that a successful exploit crosses a privilege boundary, granting high confidentiality, integrity, and availability impact. Every supported Windows client and server release is exposed, and because the component ships in default Windows installations, no unusual configuration is required once the attacker has a foothold; there is no KEV listing and no public exploit identified at time of analysis, though the low attack complexity and absence of user interaction make it an attractive post-compromise escalation primitive. Microsoft has released fixed builds, so this is a genuine prioritization candidate for patch cycles rather than an unmitigable emergency, but the hard prerequisite of existing local access is the main constraint on real-world risk.

Unauthenticated remote code execution in the Microsoft Windows DHCP Server role is achievable when an attacker on a reachable network segment wins a race condition on a shared resource inside the DHCP service. The vulnerability is rated CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), with complete confidentiality, integrity and availability impact, but the high attack complexity reflects a narrow, non-deterministic synchronization window that makes exploitation unreliable and typically requires repeated concurrent DHCP requests, potentially combined with favorable server load conditions. No public exploit code was identified at time of analysis and there is no CISA KEV listing; hosts without the DHCP Server role installed, or where DHCP traffic cannot be reached from an untrusted segment, are not exposed.

Weak authentication in the Network Device Enrollment Service (NDES) of Active Directory Certificate Services (AD CS) allows a remote, unauthenticated attacker to execute code on affected Windows Server installations. Only servers that have the optional, non-default NDES role installed and whose SCEP enrollment endpoint is network-reachable are exposed; Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025 are affected across both full and Server Core installations. The assessed vector is AV:N/AC:H/PR:N/UI:N with high confidentiality, integrity and availability impact, meaning no credentials or user interaction are needed but successful exploitation depends on attacker-uncontrollable conditions (a weak-authentication edge case), consistent with CISA SSVC Exploitation=None and Automatable=no; no public exploit has been identified at the time of analysis, and EPSS/KEV data were not provided.

Local security feature bypass in Windows UEFI (CVE-2026-49785) allows an authenticated attacker who already holds a low-privileged account on the host to defeat a boot/UEFI-related security feature, with the assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8) reflecting high confidentiality, integrity and availability impact once that local foothold exists. Exploitation is not remote and requires no user interaction, but it does require pre-existing local access and an account on the system; there is no public exploit identified at time of analysis, and CISA's SSVC framework rates exploitation as "none" with automation as "no", so this is a moderate-priority local hardening issue rather than an emergency. A vendor patch is available from Microsoft via the MSRC Security Update Guide, and the affected build ranges span most supported Windows client and server releases, including Server 2012 through Server 2025.

Rapyd Admin 9.0.0 through 9.19.x lets an authenticated company member holding the default `customer` role hijack arbitrary accounts through the Livewire `UsersModalEditEmbed` component: `editUser`, `save` and `deleteUser` trust a user id supplied by the browser and validate only a permission, so a low-privileged member can reset an owner's or super admin's password, promote themselves to `owner`, and delete users. Exploitation requires a logged-in account with the default `customer` role (which carries `edit own users`) and predictable sequential user ids - per the vendor changelog public self-registration is open, so any attacker can obtain that role, and no other non-default configuration is needed. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV); vendor-released fix: 9.20.0 (the changelog attributes the security release to 9.19.0).

Missing authorization in youlai-boot through 2.21.1 lets any authenticated user enable or disable arbitrary accounts - including root and administrator accounts - by sending a PATCH request to /api/v1/users/{userId}/status, because the updateUserStatus handler in UserController omits the @PreAuthorize('@ss.hasPerm('sys:user:edit')') guard applied to its sibling handlers. The practical impact is administrative lockout or the re-enabling of accounts an administrator had deliberately disabled; a valid login is mandatory (PR:L, authenticated per the assessed vector), no victim interaction is required, and no public exploit identified at time of analysis. This is a moderate-priority authenticated access-control flaw rather than a top-tier emergency, with impact limited to account-status toggling (integrity and availability) rather than data disclosure or code execution.

Authenticated privilege escalation in youlai-boot through version 2.21.1 lets any logged-in user grant administrator-equivalent permissions to their own role by sending a PUT request to /api/v1/roles/{roleId}/menus with arbitrary menu and button permission IDs, after which the application refreshes its Redis-backed permission cache so the elevated rights apply immediately, without re-login or administrator approval. The vulnerability is a missing authorization check (CWE-862) on a role-permission assignment endpoint rather than a memory-safety or injection flaw; exploitation requires a valid authenticated session (CVSS 4.0 PR:L, assessed CVSS:3.1 base 8.7, AV:N/AC:L/PR:L/UI:N, C:H/I:H/A:H), and the built-in GUEST test account shipped with default or demo deployments is explicitly sufficient. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit identified at time of analysis, though a public technical writeup and the upstream fix commit are available, making this a credible, non-theoretical risk within youlai-boot deployment niches rather than a mass-exploitation threat.

Any authenticated low-privilege user on iFlytek SkillHub through 0.2.22 can permanently destroy other users' skills by calling DELETE /api/cli/v1/skills/{namespace}/{slug}, because the CLI delete path performs no ownership or role check (CWE-862) even though the caller is authenticated (CVSS vector PR:L, no admin rights, no UI interaction, default configuration). Targets are trivial to enumerate because the skill search endpoint is anonymous, and a successful call cascades into a hard purge of every version, file, review, rating and metadata record, giving high integrity and availability impact with no confidentiality impact. No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis; the practical exposure is highest on publicly registrable or multi-tenant instances, while instances that disable self-registration or restrict accounts to trusted users are materially less exposed.

Configuration data leakage in Stonewuu ai-fusion-video 1.2.0 and earlier lets any authenticated non-admin user read the api-config get/list and system config endpoints, which return stored AI provider API keys, proxy passwords and mail_password values in plaintext. Because the controller methods (ApiConfigController and SystemConfigController) never verify the caller's role, a low-privilege account is enough to harvest credentials that enable AI-billing abuse and sending mail from the platform's own mail server; the vulnerability is rated CVSS 7.1 (v4.0, PR:L) and an independent assessment scores it CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, i.e. a confidentiality-only exposure that requires credentials to reach. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis and no EPSS value was supplied, which keeps this a genuine but bounded, second-order risk rather than a top-tier emergency.

Authenticated users of Wukong AICRM (versions up to and including the 20260610 release) can retrieve the cleartext AI provider API key stored in the CRM's system configuration, because the /systemConfig controller enforces no authorization check on the relevant endpoints. Any low-privilege account can call GET /systemConfig/byType/ai to read the key directly, or post an attacker-controlled apiUrl to /systemConfig/ai/test to have the server forward the stored key to a host the attacker controls. Exploitation requires a valid account (PR:L per the CVSS 4.0 vector) and only works if an AI provider key has actually been configured; no public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).

Missing authorization in Wukong AICRM through 20260610 allows any authenticated user, without administrator privileges, to invoke user, role, department, and agent administration APIs and take over the administrator account. By sending a POST to /managerUser/updateUser, an attacker with any valid low-privileged account can reset the admin password and assign themselves the 'all' role, achieving full administrative control. The flaw is rated CVSS 8.7 (High) with network reachability, low attack complexity, and no user interaction; no CISA KEV entry was present and no public exploit identified at time of analysis.

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 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.

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.

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.

Unauthenticated account takeover in Dockhand before 1.0.45 lets any remote attacker who can reach the HTTP API reset the password of the administrative or any other user account and seize it outright. The flaw chains two design failures: a global authentication hook that deliberately skips any request path ending in a static-asset extension such as .js - including paths under /api/ - and user-mutation handlers that fail open when no authenticated principal is present, so a single unauthenticated PUT to /api/users/<id>.js rewrites that user's credentials. No authentication, user interaction, or non-default configuration is required, and there is no public exploit code identified at time of analysis; the only real limiting factor is whether an attacker can reach the Dockhand API over the network, since the flaw is rated 10.0 (CVSS 4.0) and scores CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H on independent assessment. Vendor patching is available, making unpatched internet-facing instances the primary exposure.

Privilege escalation in Dockhand before 1.0.50 allows an attacker who holds administrative rights in a different tenant of a shared OIDC provider such as Microsoft Entra ID to obtain Dockhand administrator access by recreating the group Dockhand maps to its admin role and signing in, because the application fails to validate the OIDC iss, aud, nonce, and exp claims. The issue is rated CVSS 4.0 9.2 (critical) on network reach, no privileges required on Dockhand itself, no user interaction, and full confidentiality, integrity, and availability impact once admin access is obtained, though exploitation requires a shared multi-tenant IdP deployment and knowledge of the mapped group name, so single-tenant or isolated IdP deployments are not affected. No public exploit identified at time of analysis and the vulnerability is not in CISA KEV; a vendor patch is available in 1.0.50.

Improper path-equivalence handling in Microsoft Windows SmartScreen allows an unauthenticated, remote attacker to bypass the reputation/Mark-of-the-Web check so that a crafted file runs without the expected SmartScreen warning, provided the victim opens it (user interaction required, CVSS 8.8). Only unpatched Windows 11 builds are affected - 24H2 before 10.0.26100.9711, 25H2 before 10.0.26200.9711, 26H1 before 10.0.28000.3231, and 26H2 before 10.0.26300.9711; no public exploit code has been identified at time of analysis, and CISA's SSVC assessment records exploitation as 'none' and not automatable, so urgency signals conflict between the high CVSS score and total technical impact and the absence of observed or automated exploitation. A vendor patch is available and should be applied through the normal Windows update channel.

An authenticated local attacker can exploit an untrusted search path in Microsoft .NET Framework to bypass a security feature and potentially execute arbitrary code, affecting versions 3.5, 4.6.2-4.7.2, 4.8, and 4.8.1 not patched to the latest builds. The vulnerability requires local access and the ability to write a malicious file to a directory in the .NET assembly search order, but no user interaction. No public exploit code has been identified, and CISA's SSVC reports no observed exploitation; vendor patches are available.

Authentication spoofing in Microsoft Active Directory Federation Services (AD FS) allows an unauthenticated, network-positioned attacker to bypass federated authentication and have forged identity assertions accepted by an affected deployment, yielding a CVSS 3.1 score of 7.5 driven entirely by high integrity impact (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N). The weakness is an authentication bypass by spoofing (CWE-290) hitting the AD FS role on Windows Server 2012 R2, 2012 R2 Server Core, 2016, 2019, 2022, 2025, and the associated Windows 10 and Windows 11 client builds that Microsoft lists in the same update. No public exploit code exists and Microsoft's update is available, so this is a genuine patch-now exposure issue for organizations that actually run AD FS endpoints reachable by untrusted networks, not for hosts that have no AD FS role or are already at the fixed builds (for example Windows Server 2025 10.0.26100.33650, Server 2019 10.0.17763.9376, Server 2016 10.0.14393.9612, Server 2012 R2 6.3.9600.23470).

Code execution that crosses the guest-to-host boundary in Microsoft Windows Hyper-V can be triggered by an authenticated, low-privileged attacker who already runs code inside a guest virtual machine, letting them escape the VM and affect the host partition. The weakness is an access-control flaw in the hypervisor (CVSS 3.1 base 8.8, AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), so it is a local privilege and tenancy escape rather than a remotely reachable path, and a guest foothold is a hard prerequisite. No public exploit has been identified at time of analysis, but the risk is concentrated on hosts running untrusted, multi-tenant, or otherwise attacker-reachable guests.

Unauthenticated information disclosure in Microsoft Dynamics 365 Business Central allows any attacker who can reach an affected instance over the network to read sensitive data without credentials, user interaction, or any special client-side condition (CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). The flaw is root-caused to CWE-306 (Missing Authentication for Critical Function) and is strictly a confidentiality issue: no data modification or service disruption results from the bug itself, and no public exploit identified at time of analysis. Practical risk is governed almost entirely by network reachability and patch level, making this a credible, above-average-priority information-disclosure flaw rather than an emergency.

An untrusted pointer dereference (CWE-822) in the Windows Distributed File System (DFS) component allows unauthenticated remote attackers to elevate privileges on affected, unpatched Windows and Windows Server builds, per the CVSS vector AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact (9.8). Every Windows 10 branch (1607 through 22H2), Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2012 through 2025 - including Server Core installations - are listed as affected below their respective fixed builds. No public exploit code or active exploitation is confirmed at time of analysis (SSVC Exploitation: none), though EPSS is 1.15% (66th percentile), SSVC Automation: yes and Technical Impact: total, and the priority label is act_now; the practical limiting factor is network reachability of the DFS service.

Spoofing in Windows Schannel allows an unauthenticated attacker positioned on the network path between a client and server to interfere with TLS session establishment, potentially bypassing authentication and compromising confidentiality and integrity. Microsoft rates this CVSS 9.0, while our independent assessment assigns a modified vector with no availability impact (A:N) and notes that exploitation requires high attack complexity (AC:H) due to the need for a man-in-the-middle position and specific handshake/timing conditions. No public exploit identified at time of analysis.

An authorization bypass in the Ente server (the self-hosted/cloud 'museum' backend) lets an emergency contact who was already added and accepted by a victim call POST /emergency-contacts/approve-recovery with their own client-supplied user ID and a recovery-session UUID, prematurely moving the victim's emergency recovery session from WAITING to READY, clearing the wait_till value, and skipping the owner-configured notice period to retrieve recovery information. The same insufficiently scoped update pattern affects the reject and stop transitions, so any party who merely knows another user's recovery-session UUID could cancel a session they are not part of. Exploitation requires authenticated access as an established, victim-approved emergency contact and does not create recovery rights over arbitrary accounts; there is no confirmed active exploitation and no public exploit identified at time of analysis, though the vulnerability is scored 7.1 and fixed in server image 2026.07.09.

Microsoft QUIC (MsQuic) can be made to bypass a security feature over the network because a security-relevant variable is initialized to an insecure default (CWE-453), producing a CVSS 7.5 condition with no confidentiality impact, limited integrity impact and full availability impact (AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:H). The issue is unauthenticated and requires no user interaction, but is only reachable on hosts that actually run a network-exposed QUIC listener - HTTP/3 or SMB over QUIC - and the high attack complexity reflects a timing/transient-state prerequisite the attacker cannot directly control. No public exploit identified at time of analysis, and the CVE is not listed in CISA KEV; the MSRC update guide is the authoritative source for affected builds and fixes.

Type confusion (CWE-843) in Microsoft .NET and Visual Studio allows an unauthenticated remote attacker to elevate privileges when a victim opens, loads, or builds attacker-supplied content in developer tooling, rated CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not zero-click: an attacker must socially engineer a developer into processing a malicious file, project, or package so the type-confusion code path is reached, and the practical limiting factor remains that user-interaction requirement. No CISA KEV entry, no public exploit code, and no EPSS data were provided at time of analysis, so this is a credible high-priority issue but with important caveats.

Unauthorized privilege elevation in Microsoft SharePoint is possible through improper verification of cryptographic signatures, allowing unauthenticated remote attackers to forge authentication tokens and gain elevated access. Rated CVSS 8.1, the flaw requires high attack complexity but no user interaction, and the JWT-attack tag indicates it likely involves defeating JSON Web Token signature checks. No public exploit has been identified at time of analysis.

Privilege escalation in Microsoft SharePoint lets an authenticated, low-privileged user send crafted requests over the network and gain high-integrity read and write access across the affected deployment, yielding a CVSS v3.1 base score of 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation requires valid credentials on the target farm, so anonymous or fully unauthenticated attackers cannot trigger it; the realistic threat population is existing users, compromised accounts, or attackers who can self-register on internet-exposed farms. No CISA KEV entry and no public exploit code were identified at time of analysis, and no EPSS score was supplied - although external intelligence is sparse, the low attack complexity, network reachability, and lack of user interaction make this a genuine prioritisation item for SharePoint administrators.

Privilege escalation in Microsoft SharePoint allows an authenticated low-privileged user to invoke functionality that lacks a proper authorization check, yielding high confidentiality, integrity, and availability impact (CVSS 8.8, AV:N/AC:L/PR:L/UI:N) without any user interaction. Only attackers who already hold a valid low-tier SharePoint account - a standard site member, guest, or compromised credential - can exploit this over the network; a fully unauthenticated outsider cannot. No public exploit code and no CISA KEV entry were identified at time of analysis, but the missing-authorization pattern is attractive for lateral escalation once a foothold exists, making multi-tenant, extranet, and internet-facing SharePoint deployments with liberal low-privilege account provisioning the highest-risk environments.

Privilege escalation in Microsoft SharePoint allows an authenticated attacker with low-level privileges to gain elevated access over the network without user interaction. The vulnerability arises from improper access control (CWE-284) and is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), enabling high impact to confidentiality, integrity, and availability. No public exploit code has been identified at time of analysis, and the flaw is not listed in CISA KEV as actively exploited.

Missing authorization in Visual Studio Code lets a local attacker bypass a security feature once the victim opens attacker-controlled content, such as a crafted workspace, folder, or file, producing high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). No pre-existing privileges or authentication are required, but exploitation demands local delivery of the malicious content plus mandatory user interaction, which rules out remote, unattended, or automated mass exploitation. No public exploit code has been identified at time of analysis, and the specific security feature being bypassed is not detailed in the available data and should be confirmed against the Microsoft MSRC advisory.

Security feature bypass in Visual Studio Code allows an unauthenticated local attacker to bypass a security control by convincing a victim to open crafted content, such as a malicious file, folder, or workspace. Exploitation requires local access and user interaction (AV:L/UI:R) with high attack complexity (AC:H), and no public exploit code has been identified at time of analysis. This is a moderate-priority issue rather than a drop-everything emergency, and the CVSS 7.0 score reflects that.

Improper resolution of path equivalence (CWE-41) in Visual Studio Code allows an unauthenticated local attacker to bypass a security feature, likely Workspace Trust or restricted mode, by convincing a victim to open and interact with a crafted workspace or folder. The vulnerability requires user interaction and high attack complexity, and while it has a CVSS score of 7.7 (High), it is a moderate-priority developer-workstation issue rather than an internet-facing emergency. No public exploit code has been identified at time of analysis, and the exact affected versions should be confirmed via the linked Microsoft advisory.