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.
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.
Incorrect authorization in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source lets remote, unauthenticated attackers bypass security controls to gain unauthorized read access plus limited write access, with no user interaction required. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N (base 7.2) confirms the attacker needs no credentials and only network reachability to an affected, unpatched instance - typically an internet-facing storefront, REST/GraphQL API, or admin interface - while the changed scope (S:C) indicates the bypass can reach resources outside the vulnerable component's own security boundary. Impact is bounded rather than catastrophic: confidentiality and integrity are Low and availability is None, so this is a security-feature/authorization bypass rather than full administrative takeover or data destruction, and no public exploit code has been identified at time of analysis, making this a genuine but mid-tier priority.
Local privilege escalation in Windows Hyper-V allows an authorized attacker with high privileges on a host where the Hyper-V role is enabled to trigger a heap-based buffer overflow (CWE-122) and potentially corrupt hypervisor memory, leading to elevation of privilege. The attack is local only (AV:L) and requires high privileges (PR:H), user interaction (UI:R), and a difficult-to-achieve precondition (AC:H), with scope change (S:C) indicating potential impact beyond the hypervisor's security context. CISA's SSVC assessment rates Exploitation as none and Automatable as no; no public exploit code has been identified at time of analysis, and Microsoft has released a vendor patch.
SQL injection in Fortinet FortiAnalyzer and FortiManager (including Cloud variants) allows an authenticated attacker to execute arbitrary commands on the underlying system via crafted requests. Affected versions include FortiAnalyzer 7.6.0-7.6.4, 7.4.0-7.4.7, and all 7.2 releases, plus FortiManager 7.6.0-7.6.4, 7.4.0-7.4.6, and all 7.2 releases, as well as FortiAnalyzer Cloud 7.6.2-7.6.4, 7.4.1-7.4.7, 7.2.1-7.2.11 and FortiManager Cloud 7.6.2-7.6.4. The vulnerability requires valid credentials; the provided CVSS vector indicates high privileges (PR:H) while the description and independent assessment suggest low privileges (PR:L) may suffice. No public exploit code or active exploitation is identified at time of analysis, and the risk is considered elevated but not an emergency based on current signals.
Authenticated SQL injection in the Fortinet FortiAnalyzer and FortiManager management platforms allows a logged-in low-privileged user to execute arbitrary commands on the appliance via crafted requests. Affected firmware covers FortiAnalyzer 7.6.0 through 7.6.4, 7.4.0 through 7.4.7 and all 7.2 releases, plus FortiManager 7.6.0 through 7.6.4, 7.4.0 through 7.4.6 and all 7.2 releases. Exploitation requires a valid account on the management interface - the vendor CVSS vector marks PR:H while the description and independent assessment indicate a low-privileged user suffices - and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, so the main risk mitigation is limiting who can reach and authenticate to the management plane.
Stored cross-site scripting (XSS) in the AcyMailing WordPress plugin (versions up to and including 11.1.0) allows unauthenticated attackers to inject malicious scripts via the customField[] parameter of the public frontusers::subscribe endpoint. The injected script executes when a victim accesses the online-archive URL for the poisoned subscriber, potentially including administrators who click a plugin-generated link in the Subscribers → History screen. No public exploit code has been identified at time of analysis.
Stored cross-site scripting in the WordPress plugin Bit Integrations (Form Integration, Webhook, Spreadsheets, CRM, LMS & Email Automation) through version 2.10.6 lets unauthenticated remote attackers inject arbitrary JavaScript that executes for any user viewing the affected notification page, but only after a site administrator has bound a public Bit Assist webhook trigger to a BuddyBoss 'Send Notification' action, mapped an attacker-controllable form field to the notification_content parameter, and the attacker knows the flow's secret UUID callback URL. Because of those non-default configuration prerequisites the realistic exploitability is materially lower than the raw 7.2 base score suggests, which is why the authoritative assessment rates attack complexity as High (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) rather than Low. No public exploit code and no CISA KEV entry were identified at time of analysis.
Use-after-free in the Windows Enterprise App Management component lets an attacker with valid low-level credentials on a target machine, who can reach that machine over the network, corrupt freed memory and elevate to a higher-integrity context. Exploitation is gated by three limiters recorded in the assessed vector: the attacker must already hold a valid account on the target (PR:L), a victim user must perform an interaction (UI:R), and the memory-reuse race that gives an attacker control of the freed object is non-deterministic (AC:H) - so although the attack vector is network-reachable, real-world reliability and prerequisites keep this a moderate-priority issue rather than an emergency. Microsoft has released fixes in the current Windows cumulative updates, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Server-side request forgery in Adobe ColdFusion 2023 (up to and including 2023.0.25) and ColdFusion 2025 (up to and including 2025.0.13) allows an authenticated low-privileged attacker to coerce the application server into issuing requests to internal resources, yielding elevated access and disclosure of data outside the attacker's intended scope. Adobe assigns this a CVSS 3.1 base score of 7.1 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N); exploitation is non-deterministic because the vendor states success depends on conditions beyond the attacker's control, and it requires an existing foothold as a low-privileged account. There is no public exploit identified at time of analysis and no CISA KEV listing, so the practical risk profile is that of a moderate-severity, post-authentication SSRF rather than a remotely exploitable unauthenticated flaw.
Lenve vhr through commit 03abbd3 exposes BCrypt password hashes, phone numbers, and addresses for all operators to any authenticated user who requests GET /chat/hrs. A low-privileged operator account (CVSS PR:L) is sufficient, making this a confidentiality-only privilege-escalation enabler if weak hashes are cracked offline; the assessed impact is CVSS 7.1 with no integrity or availability impact. No CISA KEV confirmation or public exploit code was identified at time of analysis.
Memory-safety failure in the Windows Bluetooth Port Driver lets a device within Bluetooth radio range trigger out-of-bounds memory access that can escalate to code execution on unpatched Windows 10, Windows 11, and Windows Server hosts with an active Bluetooth radio. Exploitation requires proximity (adjacent network), the victim's Bluetooth to be enabled and in use, some form of user interaction such as accepting or initiating a Bluetooth connection, and high attack complexity reflecting preconditions outside the attacker's control; authentication is not required (CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H). Microsoft has shipped fixes, no public exploit code has been identified at time of analysis, CISA's SSVC assessment records exploitation as "none" with the attack assessed as non-automatable, and hosts with Bluetooth disabled are not exposed - making this a moderate rather than top-tier priority despite the 7.1 score and the CVSS "total" technical impact rating on affected devices.
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.
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 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).
Path traversal in Commvault HyperScale MediaAgents allows an authenticated low-privileged user to read files outside the intended directory over the network, resulting in unauthorized disclosure of data (rated 7.1, confidentiality-only impact with no integrity or availability effect). The flaw requires a valid session to the MediaAgent service (PR:L per the assessed vector), so anonymous internet attackers cannot trigger it - stolen, shared, or insider credentials are the realistic precondition. No public exploit code and no confirmed active exploitation were identified at time of analysis, and Commvault reports that software customers should upgrade to the resolved maintenance release; exact affected versions and deployment modes should be confirmed against advisory CV_2026_10_8.
Authenticated attackers with minimal privileges can disconnect active sessions of other users, including administrators, in Siemens RUGGEDCOM CROSSBOW versions prior to V6.0 due to missing authorization checks on device-disconnection requests, causing a denial of service. The flaw is network-reachable, requires low privileges (PR:L) and no user interaction, and affects only availability (VA:H) with no confidentiality or integrity impact. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.