Privilege elevation in Microsoft Exchange Server lets an authenticated low-privilege attacker forge or tamper with a signed security token that the server improperly validates, achieving full compromise of confidentiality, integrity, and availability on the affected build (CVSS 3.1 base 7.5, CWE-347). The flaw affects Exchange Server 2016 CU23 (below 15.01.2507.077), Exchange Server 2019 CU14 (below 15.02.1544.050) and CU15 (below 15.02.1748.055), and Exchange Server Subscription Edition RTM (below 15.02.2562.056); fully patched builds are not exploitable. Exploitation requires a pre-existing low-privilege identity on the server plus conditions outside the attacker's control (AC:H), CISA's SSVC rates exploitation as none and automatable as no, and no public exploit identified at time of analysis.
Improper certificate validation in the CAI Content Credentials SDK enables a network-positioned attacker who can intercept TLS connections to bypass security features and gain unauthorized write access. Exploitation requires a man-in-the-middle (MITM) position to supply a forged or invalid certificate that the SDK accepts; the assessed CVSS vector is AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N, and although the input CVSS 7.5 vector lists AC:L, our assessment raises attack complexity because the MITM prerequisite limits opportunistic mass exploitation. No user interaction or credentials are needed once the MITM position is obtained. No public exploit identified at time of analysis.
Use-after-free in Microsoft's Network Policy Server (NPS) allows an unauthenticated attacker on an adjacent network to execute arbitrary code in the context of the NPS service. Only Windows hosts that have the NPS role installed and reachable as a RADIUS/authentication server are exposed - hosts without NPS enabled cannot be triggered. Practical exploitation is constrained by high attack complexity (AC:H), since reliably winning the race/heap-shaping window is difficult, and no public exploit has been identified at time of analysis; Microsoft has released vendor patches, CISA's SSVC assessment rates exploitation as none and automatable as no, and EPSS/KEV data were not provided for this CVE.
Cross-origin redirect handling in the dio_http2_adapter plugin for Dart/Flutter copies sensitive request headers to a different origin, leaking Authorization, Cookie, Cookie2, Proxy-Authorization, Proxy-Authenticate, and WWW-Authenticate values to any server an application is redirected to. All versions from 1.0.0 up to (but excluding) 2.8.0 are affected, and only applications that use Http2Adapter (an optional HTTP/2 plugin, not Dio's default adapter) while sending credentialed requests and following redirects - which is on by default - are exposed; the attacker must control or compromise the contacted server or sit on-path to return the cross-origin Location header. The issue is unauthenticated from the attacker's perspective (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, 7.5, confidentiality-only impact) and there is no public exploit identified at time of analysis and no CISA KEV listing; the vendor-released patch is http2_adapter 2.8.0.
Remote code execution in Microsoft SQL Server 2022 and 2025 arises from a stack-based buffer overflow (CWE-121) that is triggered when a client connects to an attacker-controlled SQL Server endpoint and the malicious response overflows a fixed-size stack buffer. The vulnerability is unauthenticated from the attacker's side (PR:N) but requires victim-side interaction (UI:R) and high attack complexity (AC:H), so it is a moderate-priority issue rather than a mass-exploitation emergency; no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation. Affected builds are SQL Server 2022 GDR below 16.0.1210.3 and CU27 below 16.0.4305.5, plus SQL Server 2025 GDR below 17.0.1145.4 and CU9 below 17.0.5015.4, with vendor-released patches available from Microsoft.
Unauthenticated remote denial of service affects SAP NetWeaver and SAP Web Dispatcher deployments in which the Internet Communication Manager (ICM) internal protocol component can be reached by an attacker; a specially crafted request carrying invalid field values triggers an integer underflow (CWE-191) that corrupts memory handling and crashes the affected process. The flaw is rated CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning any network-reachable instance is exposed with no credentials or user interaction required, but the consequence is strictly service disruption - there is no confidentiality or integrity impact and no demonstrated path to data disclosure, tampering, or code execution. Exploitation status: no public exploit identified at time of analysis, and no CISA KEV entry or EPSS score was supplied; the practical risk driver is therefore exposure of the ICM/Web Dispatcher protocol endpoint rather than active exploitation, with internet-facing systems materially more at risk than segmented internal ones.
IBM WebSphere Application Server - Liberty (20.0.0.12 through 26.0.0.10) can be driven into a denial-of-service condition by a remote attacker whose request raises an uncaught exception, degrading availability with no confidentiality or integrity impact. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication, privileges or user interaction are required - the only prerequisite is network reachability to an affected Liberty instance, and the exact endpoint or feature that triggers the fault is not described in the available sources. Exploitation has not been confirmed (CISA SSVC: Exploitation none) and no public exploit code has been identified; EPSS is low at 0.32% (23rd percentile), and the CISA SSVC assessment rates automation as possible but technical impact as partial, so prioritization within a weekly patch cycle is appropriate rather than emergency action.
Improper certificate validation in the CAI Content Credentials SDK allows remote, unauthenticated attackers to bypass security features and gain unauthorized write access (CVSS 7.5, High). Exploitation requires the attacker to present a forged or untrusted certificate that the SDK incorrectly accepts, and no user interaction is needed. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Improper certificate validation in Adobe's CAI Content Credentials SDK (Content Credentials SDK) allows remote, unauthenticated attackers to bypass certificate trust checks and gain unauthorized write access, effectively letting them forge or tamper with signed Content Credentials data with no user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5). Impact is bounded to integrity - no confidentiality or availability effect - and only deployments that actually invoke the SDK to validate Content Credentials certificates are exposed. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; exploitation in practice requires the attacker to supply crafted signed content or hold a man-in-the-middle position on the certificate validation path.
Improper certificate validation (CWE-295) in the CAI/Adobe Content Credentials SDK allows an unauthenticated remote attacker to have forged or self-signed signing certificates accepted during C2PA manifest verification, bypassing the provenance trust check and enabling unauthorized write (integrity) impact - CVSS 3.1 base 7.5, vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. No user interaction is required, but exploitation is not automatic: the attacker must get crafted content into a workflow that validates it with the vulnerable SDK, or occupy a trust/transport position from which a malicious certificate is presented, which is narrower in practice than the network-vector score implies. There is no CISA KEV listing and no public exploit identified at time of analysis; impact is confined to integrity, with no confidentiality or availability loss indicated.
Local privilege escalation in WSUS (Windows Server Update Services) allows an authenticated low-privileged attacker with local access to elevate privileges by exploiting incorrect default permissions (CWE-276). The vulnerability has a Microsoft-assigned CVSS 3.1 score of 7.5 (AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H), indicating high attack complexity and required user interaction, but it can lead to full compromise of confidentiality, integrity, and availability. No public exploit identified at time of analysis, and a patch is available per the Microsoft advisory.
An off-by-one heap buffer overflow in libconfini 1.16.4's bundled example utility load_ini_buffer (examples/utilities/load_ini_buffer.h) can crash the process that embeds it, producing a denial of service. The flaw is only reachable when consuming software actually compiles and feeds attacker-influenced input to that example utility; it is not reachable through the core libconfini parsing API alone, and impact is availability-only with no code execution or data disclosure indicated. Exploitation requires an unauthenticated network-reachable path into the affected utility (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L per independent assessment, versus the submitter's N/A:H rating), and no public exploit has been identified; EPSS is 0.29% (20th percentile), consistent with a low-to-moderate real-world priority.
Denial of service is possible in libwebsockets because the LEJP JSON parser's pre-patch bounds checks in lib/misc/lejp.c permit a one-past-the-end write into the fixed-size ctx->i[] and ctx->st[] arrays when deeply nested JSON is parsed. The flaw is remotely reachable and unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5), but the affected target is the main-branch commit 106d542c rather than a confirmed released version, and exploitability depends entirely on whether the host application routes attacker-controlled JSON into lejp_parse(); impact is limited to availability (a crash), with no code execution or data disclosure indicated. EPSS is 0.29% (20th percentile), the issue is not in CISA KEV, and no public exploit has been identified at time of analysis, although upstream fixes exist in commits 736a4a2 and c404a20.
Use-after-free in the Windows Bluetooth Port Driver (bthport.sys) lets an attacker positioned within Bluetooth radio range of an unpatched Windows host elevate privileges, with no authentication and no user interaction required (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, 7.5 High). Real-world risk is constrained by high attack complexity - the attacker must reliably win a non-deterministic race in driver memory handling - and by the prerequisites of physical proximity and an active Bluetooth stack; CISA's SSVC assessment records no observed exploitation and no automatable path (Technical Impact: total). Microsoft has published vendor patches, and no public exploit code has been identified at time of analysis.
Denial of service in libass 0.17.5: rendering a crafted ASS/SSA subtitle drives 32-bit integer overflow in ass_outline_construct() and the surrounding bbox, pen-advance and shear arithmetic in libass/ass_render.c, causing the hosting application to crash or abort. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) the issue is remotely reachable without authentication, but the attacker must first get a malicious subtitle parsed and rendered - as an embedded or sidecar track in a media file, or an auto-processed subtitle in a server-side pipeline - and the effect is limited to availability with no confidentiality or integrity impact. A public PoC reference exists (a gist is linked from the CVE record); it is not verified as working exploit code, EPSS is low at 0.26% (17th percentile), there is no CISA KEV listing, and the priority signal is this_week rather than emergency.
Origin-validation bypass in Microsoft .NET 8.0, 9.0, 10.0 and 11.0 (plus bundled Visual Studio 2022 17.14 and Visual Studio 2026 18.10 builds) lets an unauthenticated remote attacker defeat a built-in security feature when a victim interacts with attacker-supplied cross-origin content, producing integrity-only impact (CVSS 6.5, I:H with no confidentiality or availability loss). The mandatory user-interaction step (UI:R) and the fact that exploitation depends on the application actually relying on the affected origin-checking feature keep this at moderate severity; there is currently no public exploit identified at time of analysis, CISA SSVC records exploitation as none and automation as no, and EPSS/KEV data is absent. Vendor patches are available (MSRC advisory msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96238).
A guest domain on a Xen hypervisor can corrupt memory belonging to another domain by issuing GNTTABOP_cache_flush with invalidate-without-clean semantics against a read-only grant mapping it was given, because the hypervisor does not reject that operation/mapping combination. Only multi-tenant or disaggregated Xen deployments that actually share pages between domains through the grant table are exposed, and the attacker must already be running code in a guest (assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N). Impact is silent integrity corruption of the granting domain's data rather than a crash or leak; EPSS is 0.15% (3rd percentile) and no public exploit identified at time of analysis.
Guest-triggered denial of service in Xen Hypervisor can drive 64-bit Arm hosts into an excessively long cache-flush loop and likely crash the hypervisor. The issue is an integer underflow in the GNTTABOP_cache_flush grant-table path introduced by the earlier XSA-437 fix; an attacker able to run code in a guest and issue the hypercall can exhaust host CPU and availability. No public exploit was identified at time of analysis, and EPSS is low at 0.15%.
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.
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.
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.
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.
Plugin installation in Claude Code and Claude Desktop before 2.1.179 can install attacker-controlled code: the installer pins a plugin to a 40-character commit SHA from a marketplace but then runs git checkout on that string without confirming that the resulting HEAD actually equals the pinned SHA, so an attacker who controls the plugin repository on a Git host that allows branch names shaped like a 40-hex SHA can create a branch named after the 'reviewed' commit and have its tip checked out instead. Exploitation is unauthenticated from the attacker's side (CVSS 4.0 vector PR:N) but requires considerable user interaction - the victim must choose to install the malicious plugin and deliberately pin it to the ostensibly safe hash - which is why our independent assessment rates it a HIGH-impact, LOW-likelihood issue that is a moderate, conditional priority rather than an emergency. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation: none and Automatable: no, and there is no KEV listing.
Information disclosure in Microsoft Azure HDInsight (version 1.0 below build 2606012120) allows a remote, unauthenticated attacker requiring no user interaction to read sensitive data from network-reachable clusters, as reflected by the assessed CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), which caps impact at high confidentiality loss with no integrity or availability effect. This is a genuine but moderate-priority issue: it is tracked as EUVD-2026-99575, is reported by secure@microsoft.com, and a vendor patch is indicated, though no public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS score was supplied. Because HDInsight is a Microsoft-managed service, the practical exposure depends heavily on whether the target cluster is still running an unpatched build and whether its endpoints are network-reachable.
Unauthenticated remote denial of service in the Active Directory Federation Services (AD FS) role on Windows Server: a network attacker who can reach the AD FS listener can drive unbounded resource allocation (CWE-770), exhausting memory/threads/connections and taking the federation service offline. Per the assessed vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, no credentials, privileges, or user interaction are required against a default-configured service; exploitability is gated purely by whether the AD FS endpoints are reachable by untrusted clients (internet-published or untrusted-segment federations are the exposed case, while non-exposed or AD FS-less hosts are not affected). Affected builds span Windows Server 2012 R2 through 2025 below their patched build levels, and the vendor has released patch data; no public exploit has been identified at time of analysis and CISA SSVC records Exploitation: none, so this is a genuine but bounded availability risk rather than an active campaign. Impact is confined to availability - there is no confidentiality or integrity loss.
Unbounded resource allocation in Microsoft Active Directory Federation Services (AD FS) lets an unauthenticated remote attacker consume server resources and degrade or deny service, with the AD FS authentication endpoint itself being the attack surface. Only hosts that actually run the AD FS role on the unpatched Windows Server 2012 through 2025 and Windows 10 1607/1809 builds listed in the vendor data are exposed, so environments that do not deploy AD FS or that keep its endpoints off the public internet are largely unaffected. The flaw is remote, low-complexity, and requires no credentials or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), and while CISA's SSVC assessment rates it automatable, exploitation has not been observed and no public exploit code or proof of concept was identified at time of analysis; the assessed impact is availability-only, with confidentiality and integrity untouched.
Memory exhaustion in the Windows DHCP Client service allows an unauthenticated attacker who can deliver crafted DHCP responses to progressively degrade or deny service on Windows 11 24H2/25H2/26H1/26H2 and Windows Server 2025 (including Server Core installations). The vulnerability is availability-only (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), with no data exposure or code execution, and the effect builds gradually as leaked memory accumulates rather than causing an immediate crash. There is no public exploit identified at time of analysis and CISA SSVC records no observed exploitation, but the attack is rated automatable, so hosts that have not been updated past their fixed build remain a practical target for anyone positioned to answer DHCP traffic on the local segment; vendor-released patches are available.
Denial of service in Windows DHCP Server allows unauthenticated remote attackers to crash the DHCP service via a null pointer dereference. Exploitation requires the DHCP Server role to be installed and running on affected builds of Windows Server 2012 through 2025 (including Server Core installations) and Windows 10 1607/1809, with the attacker able to reach the service over the network through UDP 67/68 or the RPC management interface. No public exploit code has been identified at time of analysis (CISA SSVC exploitation: none), the assessed CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, and the impact is availability-only with no confidentiality or integrity loss.
Unauthenticated remote attackers can exhaust service resources on internet-facing Microsoft Active Directory Federation Services (AD FS) deployments, causing denial of service to federated authentication. Tracked as CVE-2026-83645 (CVSS 7.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, CWE-770), exploitation requires only network reachability to an AD FS federation endpoint - no credentials, privileges, or user interaction - and the affected scope covers Windows Server 2012 through 2025 plus Windows 10 1607/1809 where the AD FS role is installed. Impact is confined to availability of the federation service with no confidentiality or integrity loss, and there is no public exploit identified at time of analysis with CISA SSVC recording no observed exploitation, making this a genuine but moderate-priority availability issue rather than an emergency.
Remote, unauthenticated denial of service in the Windows Local Security Authority Subsystem Service (LSASS) allows any network-reachable attacker to crash the process that handles logon, credential validation and authentication for the host. Affected builds span Windows 10 Version 1809, Windows 11 24H2/25H2/26H1/26H2, and Windows Server 2019, 2022 and 2025 (including Server Core installations); patched builds at or above the vendor-listed build numbers are not exploitable. The impact is availability-only - no code execution, no data disclosure and no integrity impact - so real-world exposure is mainly a concern where authentication ports are reachable and where a host reboot or loss of authentication services is operationally disruptive; no public exploit code was identified at time of analysis and there is no confirmed active exploitation.
Information disclosure in the Microsoft Azure Attestation service and the Device Health Attestation Service on Windows Server lets an unauthenticated remote attacker read out-of-bounds memory (CVSS 7.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), leaking data processed by the attestation stack. No privileges or user interaction are required, but reachability is limited to hosts that actually run and network-expose the attestation endpoint; affected builds are Windows Server 2019 below 10.0.17763.9376, Windows Server 2022 below 10.0.20348.5761, and Windows Server 2025 below 10.0.26100.33650, including Server Core installations. There is no public exploit identified at time of analysis, vendor patches are available, and impact is confined to confidentiality with no integrity or availability effect.
Unauthenticated remote denial of service affecting IBM WebSphere Application Server Liberty (17.0.0.3 through 26.0.0.10) and traditional IBM WebSphere Application Server 8.5 and 9.0, where uncontrolled resource consumption lets a network-reachable attacker degrade or exhaust server availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms no authentication or user interaction is required and that impact is confined to availability, with no confidentiality or integrity loss. At the time of analysis no public exploit code has been identified for this issue, and CISA KEV does not list it as confirmed actively exploited; IBM has published a vendor fix via its support advisory at https://www.ibm.com/support/pages/node/7292214.
Unauthenticated path traversal in the NVIDIA AIStore Promote API on Linux lets a remote attacker read arbitrary files that the AIStore process can access by supplying a crafted absolute source path, resulting in high-confidentiality information disclosure (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Any network-reachable deployment where the Promote endpoint is enabled and functional is at risk, since the vector requires no authentication (PR:N) and no user interaction (UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical blast radius is bounded by the OS privileges of the AIStore process account and by whether the Promote API is exposed beyond trusted internal networks, making this a genuine but moderate-priority issue rather than a critical emergency.
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.
Information disclosure in certain Zoom Clients' My Notes feature allows an on-path attacker who presents a fraudulent certificate to obtain feature-related data because the client fails to validate certificates properly. The vulnerability is remotely reachable without authentication or user interaction (AV:N/AC:H/PR:N/UI:N), but exploitability is constrained by the requirement to hold a man-in-the-middle position on the network path, and the independent assessment limits impact to confidentiality. No public exploit or confirmed active exploitation (CISA KEV) was identified, and no EPSS score was supplied at time of analysis.
Improper TLS certificate validation in Zoom Clients for Windows allows an attacker who already holds a man-in-the-middle position on the network path to have a forged or invalid certificate accepted by the client, exposing data in transit (CWE-295). Affected are Zoom Clients for Windows builds tracked by the vendor CPE cpe:2.3:a:zoom_communications:zoom_clients (wildcard versioning indicates the bulletin applies across the client line, with specifics in Zoom security bulletin ZSB-26021). No authentication (PR:N) or user interaction (UI:N) is required once the interception position is held, but high attack complexity (AC:H) reflects that the attacker must first compromise the network path - e.g., hostile Wi-Fi, ARP/DNS spoofing, or a compromised network device - so this is not exploitable by an arbitrary remote attacker; there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV not applicable). The reported CVSS base score of 7.4 (High) is driven by AV:N/PR:N/UI:N, and the assessed impact is high confidentiality loss with integrity impact not confirmed by our independent assessment.
Authenticated users of GitLab Enterprise Edition can inject specially crafted content into the context that AI agent features assemble, allowing unintended commands to be executed and attributed to other users. The issue affects GitLab EE from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2, and exploitation requires a valid EE account (PR:L), the AI agent/conversation feature to be enabled and in use, and a separate victim user to trigger the affected AI interaction (UI:R), so realistic exposure is substantially narrowed despite the network attack vector. No public exploit code or confirmed active exploitation was identified at time of analysis; vendor-released patches are available in versions 19.2.8, 19.3.5, and 19.4.2.
OS command injection in Azure CycleCloud allows an authenticated local user with low privileges to execute arbitrary code on the affected host, but only if a victim performs a required user interaction. The CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H with a base score of 7.3, and the independent assessment rates this as a moderate-priority issue rather than a top-tier emergency. The available data provides no public exploit identified at time of analysis and no CISA KEV confirmation; Microsoft's MSRC update-guide entry is the provided remediation reference.
Heap-based buffer overflow in Microsoft's Windows Distributed File System (DFS) lets an attacker who already holds high privileges on the target send crafted network traffic to the DFS service and achieve code execution, with high impact to confidentiality, integrity, and availability. The flaw, tracked as CWE-122, affects a broad set of Windows client and server releases-including Windows 10, Windows 11 23H2/24H2/25H2/26H1/26H2, Windows Server 2012 through 2025-and carries a CVSS of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), meaning exploitation is reliable but gated behind a significant privilege prerequisite. There is confirmed no active exploitation per SSVC (Exploitation: none) and no public exploit identified at time of analysis; CISA's SSVC also rates it non-automatable, so mass scanning and worm-style spread are not expected. The practical risk is concentrated in environments where the DFS role is deployed and network-reachable and where an attacker has already obtained administrative-equivalent access, making this a post-compromise elevation/impact vector rather than an initial access path.
Command injection in MultiTail 7.1.5 and earlier lets an attacker who can write content into a monitored log or stream execute arbitrary shell commands as the user running MultiTail, because matched text is concatenated into a command passed to sh -c with only partial escaping. Exploitation is gated by a deliberate, non-default configuration: the operator must have enabled the -ex/-eX execute-on-match feature with a filter regex, and the injected line must match that regex; because the CVSS vector is AV:L/PR:L/UI:R, this is a local, low-privileged, user-interaction-dependent issue with impact bounded by the privileges of the MultiTail process. Exploitation code is publicly available (CISA SSVC reports Exploitation: poc), but there is no evidence of confirmed active exploitation, and the assessed risk is moderate and internally consistent rather than alarming.
Mozilla Firefox prior to 158 contains a mitigation bypass in the DOM: Security component that lets remote attackers defeat a built-in browser protection, potentially enabling follow-on attacks the defense was designed to stop. The issue is rated CVSS 7.3 with low confidentiality, integrity, and availability impact; it is a defense-in-depth failure rather than direct code execution, and practical harm generally requires chaining with another vulnerability. Exploitation requires the victim to open attacker-controlled web content in an affected build, and no public exploit identified at time of analysis, with no CISA KEV activity and EPSS 0.20% (percentile 9%).
Mozilla Firefox before 158 can misrepresent Address Bar information, allowing attacker-controlled content to appear more trustworthy and potentially tricking users into entering credentials or following a spoofed destination. This is a CWE-451 UI misrepresentation issue that requires the victim to visit or interact with attacker-controlled content; independent assessment scopes practical impact to limited integrity rather than code execution or direct data access. No public exploit code was identified at time of analysis, and EPSS is low at 0.16% (4th percentile); Mozilla fixed the issue in Firefox 158.
An uncontrolled out-of-bounds read in NVIDIA DALI (Data Loading Library) can be triggered when a low-privileged local user processes specially crafted input through a DALI data-loading or augmentation pipeline (CVSS 3.1 base 7.3, AV:L/AC:L/PR:L/UI:R), resulting in memory disclosure, data tampering, and denial of service. Impact is bounded by the local attack vector and the requirement for both low privileges and user interaction - an unauthenticated remote attacker cannot trigger it directly, and an idle default installation is not exploitable. Exposure is greatest in workflows where DALI ingests untrusted or externally sourced datasets and media; the CPE record (cpe:2.3:a:nvidia:dali:*:*:*:*:*:*:*:*) indicates the issue is not version-scoped in the supplied data, and no public exploit code or CISA KEV entry has been identified at time of analysis.
An uncontrolled out-of-bounds write in NVIDIA DALI (the Data Loading Library used for GPU-accelerated data preprocessing) allows a locally positioned attacker who already holds low-level privileges to corrupt process memory when a DALI pipeline loads or decodes attacker-influenced input such as a crafted image, media file, or dataset record. A successful exploit can produce denial of service, information disclosure, and data tampering, consistent with the vendor rating of 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H), which requires local access, low privileges, and user interaction (a victim or process must ingest the malicious data). There is no CISA KEV listing and no public exploit identified at time of analysis, so practical risk is concentrated in multi-tenant training clusters, pipelines consuming externally sourced datasets, and services that accept user-submitted media for GPU preprocessing rather than in default in-house-only deployments.
An uncontrolled out-of-bounds read in NVIDIA DALI is triggered while the library parses attacker-supplied data inside a data-loading pipeline, allowing crafted input to expose process memory contents and crash the workload, which results in information disclosure and denial of service. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:H) the attack is local, requires the attacker to already hold low-level privileges on the host, and critically depends on user interaction - a user or training job must actually run DALI over the malicious sample, so environments that ingest only trusted, internally generated data are effectively not exposed. There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); this is a moderate, not top-tier, priority.
OS command injection in KDE Dolphin 24.08.0 through 26.08.2 allows an attacker who can place a specially named directory on the victim's filesystem to run arbitrary commands with the victim's privileges when that folder's empty view background is double-clicked. The flaw lies in Dolphin substituting the folder path into the {path} placeholder of a shell command without neutralizing embedded double quotes and shell metacharacters, so a directory name such as one containing a quote plus `;`, `$()`, or backticks escapes the quoting in slotDoubleClickViewBackground. This is a genuine but interaction-gated local issue rather than a mass-exploitable remote flaw: exploitation requires the crafted directory to already exist (delivered via archive, network/share, USB, or cloned repository), an affected build running, and mandatory user interaction (the background double-click); no public exploit code was identified at time of analysis, and impact stays within the victim's user scope with no scope change.
Local privilege escalation in Microsoft PowerToys allows an authenticated low-privileged attacker to tamper with an externally controllable PowerToys configuration setting and, once a legitimate or higher-privileged user or process consumes that tampered configuration, gain elevated privileges on the same host; the vendor-assigned CVSS is 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H), with high confidentiality, integrity, and availability impact. Affected are PowerToys installations from 0.1 up to but not including 0.101.2632.0 on Windows. Exploitation requires authenticated local access plus user interaction, so it is not remotely triggerable and not an unauthenticated attack path; there is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis.
Local privilege escalation in Microsoft Sysinternals allows an authenticated low-privileged attacker to elevate privileges by exploiting a stack-based buffer overflow, requiring user interaction. The vulnerability has a CVSS 3.1 base score of 7.3 (High). No public exploit code or active exploitation has been identified at time of analysis.
Stack-based buffer overflow in NVIDIA DALI lets a locally authenticated, low-privileged user who can get a crafted input file processed through a DALI pipeline corrupt memory and potentially achieve code execution, information disclosure, data tampering, or denial of service. Per the assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 7.3 High), exploitation is not remotely reachable: it requires an existing local foothold with at least low privileges plus some form of user interaction, which in practice means a victim or automated process must load attacker-controlled data. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; the practical risk concentrates on multi-tenant or pipeline-automation GPU hosts where untrusted files are routinely fed into DALI. Exact affected versions are unconfirmed because the CPE is a wildcard, so defenders must verify their deployed DALI build against the NVIDIA advisory.
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.