Monthly
Security-feature bypass in Microsoft Office Word - including the wider Microsoft 365 Apps for Enterprise and Office LTSC 2021/2024 families on Windows and macOS - lets an attacker defeat a protection mechanism such as Protected View, mark-of-the-web enforcement, or a trust/macro prompt by getting a victim to open or preview a crafted document. No attacker credentials or prior access are required (CVSS PR:N), but exploitation is local (AV:L) and depends on the target user interacting with the file (UI:R); a successful bypass yields high confidentiality, integrity, and availability impact for a 7.8 High severity rating. No public exploit code or confirmed active exploitation was identified at time of analysis, and Microsoft has released a patched update through its Update Guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-108433).
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.
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.
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).
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.
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.
Local privilege escalation in Progressive Robot hMailServer 6.3.4 and 6.3.5 on Linux allows an attacker who already has code execution as the unprivileged hmailserver service account to run arbitrary code as root via the live-update apply helper (hmailserver-update). The vulnerability requires the live-update path unit to be active, which is the default for the project's .deb and .rpm packages and applies to AppImage installations run under that unit, but does not affect non-Linux builds. No public exploit code has been identified at time of analysis, and the vendor has released version 6.3.6 to address the issue.
OS command execution in Kiteworks Core is possible when the remote-support capability is licensed and enabled and an authenticated System Administrator also possesses the key protecting submitted data, allowing that administrator to redirect the outbound support connection to an attacker-chosen destination that can then execute OS commands with local service account privileges. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, so exploitation requires high application privileges plus the additional key-possession condition, and deployments without remote support enabled are not exposed; there is no public exploit identified at time of analysis and no CISA KEV indication. The independent assessment rates real-world priority low-to-medium despite the 7.2 High base score.
Privilege escalation and remote code execution on managed hosts is possible in Red Hat Ansible Automation Platform 2 because the automation-controller exposes the provisioning-callback secret (host_config_key) to anyone holding only read-level view_jobtemplate permission and accepts a client-supplied X-Forwarded-For header as proof of caller identity when the gateway proxy allow-list is empty. An attacker who reads the secret from the job template API representation or the activity stream and spoofs X-Forwarded-For to match any host in the target job template's inventory can launch that template against arbitrary managed hosts using the template's stored credentials; CVSS 3.1 base score is 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), no public exploit code was identified at time of analysis, and the decisive enabler is a non-default deployment condition - an empty proxy allow-list combined with provisioning callbacks actually being in use.
Authentication bypass in 9Router (npm package '9router') before 0.5.6 lets a remote, unauthenticated attacker reach the public LLM API under /api/v1/* by simply adding the header X-9r-Real-Ip: 127.0.0.1, which the application's isLocalRequest() logic in src/dashboardGuard.js trusts when deciding whether canAccessPublicLlmApi() may skip API-key validation. Successful abuse grants unauthorized use of the instance owner's configured LLM providers, consumption of paid credits, and enumeration of configured providers and models; the verified affected route is GET /api/v1/models. Per the assessed vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L, 7.3), no authentication or user interaction is required, but exploitation is only possible on deployments where requests reach Next.js directly without the bundled custom-server.js wrapper and where the LLM API is network-reachable (the default bind is 0.0.0.0); instances correctly served through custom-server.js are not exploitable. The vendor advisory includes a proof-of-concept showing a 401 baseline request succeeding with 200 OK after the sole header is added.
Security-feature bypass in Microsoft Office Word - including the wider Microsoft 365 Apps for Enterprise and Office LTSC 2021/2024 families on Windows and macOS - lets an attacker defeat a protection mechanism such as Protected View, mark-of-the-web enforcement, or a trust/macro prompt by getting a victim to open or preview a crafted document. No attacker credentials or prior access are required (CVSS PR:N), but exploitation is local (AV:L) and depends on the target user interacting with the file (UI:R); a successful bypass yields high confidentiality, integrity, and availability impact for a 7.8 High severity rating. No public exploit code or confirmed active exploitation was identified at time of analysis, and Microsoft has released a patched update through its Update Guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-108433).
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.
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.
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).
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.
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.
Local privilege escalation in Progressive Robot hMailServer 6.3.4 and 6.3.5 on Linux allows an attacker who already has code execution as the unprivileged hmailserver service account to run arbitrary code as root via the live-update apply helper (hmailserver-update). The vulnerability requires the live-update path unit to be active, which is the default for the project's .deb and .rpm packages and applies to AppImage installations run under that unit, but does not affect non-Linux builds. No public exploit code has been identified at time of analysis, and the vendor has released version 6.3.6 to address the issue.
OS command execution in Kiteworks Core is possible when the remote-support capability is licensed and enabled and an authenticated System Administrator also possesses the key protecting submitted data, allowing that administrator to redirect the outbound support connection to an attacker-chosen destination that can then execute OS commands with local service account privileges. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, so exploitation requires high application privileges plus the additional key-possession condition, and deployments without remote support enabled are not exposed; there is no public exploit identified at time of analysis and no CISA KEV indication. The independent assessment rates real-world priority low-to-medium despite the 7.2 High base score.
Privilege escalation and remote code execution on managed hosts is possible in Red Hat Ansible Automation Platform 2 because the automation-controller exposes the provisioning-callback secret (host_config_key) to anyone holding only read-level view_jobtemplate permission and accepts a client-supplied X-Forwarded-For header as proof of caller identity when the gateway proxy allow-list is empty. An attacker who reads the secret from the job template API representation or the activity stream and spoofs X-Forwarded-For to match any host in the target job template's inventory can launch that template against arbitrary managed hosts using the template's stored credentials; CVSS 3.1 base score is 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), no public exploit code was identified at time of analysis, and the decisive enabler is a non-default deployment condition - an empty proxy allow-list combined with provisioning callbacks actually being in use.
Authentication bypass in 9Router (npm package '9router') before 0.5.6 lets a remote, unauthenticated attacker reach the public LLM API under /api/v1/* by simply adding the header X-9r-Real-Ip: 127.0.0.1, which the application's isLocalRequest() logic in src/dashboardGuard.js trusts when deciding whether canAccessPublicLlmApi() may skip API-key validation. Successful abuse grants unauthorized use of the instance owner's configured LLM providers, consumption of paid credits, and enumeration of configured providers and models; the verified affected route is GET /api/v1/models. Per the assessed vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L, 7.3), no authentication or user interaction is required, but exploitation is only possible on deployments where requests reach Next.js directly without the bundled custom-server.js wrapper and where the LLM API is network-reachable (the default bind is 0.0.0.0); instances correctly served through custom-server.js are not exploitable. The vendor advisory includes a proof-of-concept showing a 401 baseline request succeeding with 200 OK after the sole header is added.