CVE-2026-90442 is a stack-based buffer overflow vulnerability in the certd process of WatchGuard Fireware OS. It affects versions 2025.1 up to but not including 2026.4, 12.0 up to but not including 12.12.4, and 12.0 up to but not including 12.5.22. An authenticated attacker with access to the Firebox management interface can exploit this flaw by sending a specially crafted request, causing the certificate management service to crash and potentially allowing arbitrary code execution. The vulnerability has a high severity with a CVSS 4.0 score of 8.6. Fixed versions are 2026.4, 12.12.4, and 12.5.22.
CVE-2026-112710 is a critical heap-based buffer overflow vulnerability in the WatchGuard Fireware OS authentication service. It affects versions 2025.1 up to but not including 2026.4, 12.0 up to but not including 12.12.4, and 12.0 up to but not including 12.5.22. An attacker who can control or intercept traffic to the configured Active Directory server can exploit this flaw by sending a specially crafted response, potentially causing denial of service or arbitrary code execution. The vulnerability has a CVSS 4.0 base score of 9.2, indicating high impact on confidentiality, integrity, and availability. Fixed versions are available in 2026.4, 12.12.4, and 12.5.22.
CVE-2026-82332 is an improper authentication vulnerability in WatchGuard Fireware OS's AuthPoint multi-factor authentication process. It allows a local, unauthenticated attacker on the appliance to hijack another user's active MFA session by sending a specially crafted request and tricking the victim into accepting an MFA push notification. The vulnerability affects Fireware OS versions from 2025.1 up to but not including 2026.4, and versions from 12.7 up to but not including 12.12.4. A fix is available in versions 2026.4 and 12.12.4. The CVSS 4.0 base score is 5.6, indicating medium severity.
CVE-2026-93857 is a critical stack-based buffer overflow vulnerability in WatchGuard Fireware OS's SIP proxy. It allows a remote, unauthenticated attacker to execute arbitrary code by sending a specially crafted request through a policy that uses the SIP proxy. The vulnerability affects multiple versions of Fireware OS prior to fixed releases. A high-severity CVSS 4.0 score of 9.2 reflects the ease of exploitation and potential impact. Fixed versions are available, and users should upgrade to mitigate this risk.
CVE-2026-93866 is a critical integer overflow vulnerability in the WebSocket connection handling of WatchGuard Fireware OS's Access Portal. It allows a remote, unauthenticated attacker to write beyond the bounds of a heap buffer by sending a specially crafted request when the Access Portal feature is enabled. This vulnerability affects multiple versions of Fireware OS prior to fixed releases.
CVE-2026-93864 is a path traversal vulnerability in WatchGuard Fireware OS's firewall daemon. It allows a local attacker with low-privileged code execution to overwrite arbitrary files with root privileges by planting a crafted file system object and triggering a list update. This can also lead to tampering with firewall IP set data. The vulnerability affects multiple versions of Fireware OS and has been assigned a high severity rating with a CVSS score of 7.1. Fixed versions are available.
CVE-2026-103594 is a critical stack-based buffer overflow vulnerability in WatchGuard Fireware OS affecting the WireGuard configuration processing. A remote attacker with man-in-the-middle TLS-decrypted access between the Firebox and WatchGuard Cloud can exploit this flaw to cause a denial of service or potentially execute arbitrary code by tampering with a FireCloud Gateway configuration payload. The vulnerability affects Fireware OS versions from 2026.2 up to but not including 2026.4, and versions from 12.12 up to but not including 12.12.4. Fixed versions are 2026.4 and 12.12.4.
CVE-2026-104381 is an authentication bypass vulnerability in WatchGuard Fireware OS affecting the FireCluster state synchronization feature. An unauthenticated attacker on the cluster synchronization network segment can send crafted traffic to prematurely terminate VPN tunnels. The issue affects multiple versions prior to fixed releases 2026.4, 12.12.4, and 12.5.22. The vulnerability has a medium severity rating with a CVSS 4.0 score of 6. No known exploits are reported in the wild.
CVE-2026-111107 is a high-severity vulnerability in WatchGuard Fireware OS management interface that allows remote unauthenticated attackers to crash the management service via a specially crafted login request. This causes a NULL pointer dereference, terminating all active administrator sessions and ongoing management operations. The vulnerability does not affect traffic processing through the device. Fixed versions are available.
CVE-2026-93865 is a critical vulnerability in WatchGuard Fireware OS affecting the FireCluster synchronization daemon. It allows a remote, unauthenticated attacker to perform privileged system-level administrative actions by sending specially crafted requests to the FireCluster management IP when clustering is enabled. The flaw is due to missing authentication for a critical function. Fixed versions are available.
The npm package 'string-target-mapper-hash' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removal of the package alone does not guarantee elimination of all malicious software, as the attacker may have gained full control of the system.
The npm package 'macro-kernel-record-reader' is identified as containing malicious code. Any system with this package installed or running is considered fully compromised, potentially allowing an attacker full control over the computer. Immediate rotation of all secrets and keys stored on the affected system is recommended, using a different, uncompromised machine. Removal of the package is advised, but it may not fully eliminate the malicious presence due to possible persistent backdoors or additional malware installed.
The npm package 'fetch-hash-cache-atomic' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a separate, trusted machine. Removal of the package alone is insufficient to guarantee the elimination of all malicious software introduced by this package.
CVE-2026-109823 is a vulnerability in tidewave versions from 0.8.0 up to but not including 0.9.2 that allows an attacker to read filesystem path names exposed via Tidewave configuration endpoints and the rendered toolbar. The issue arises because responses do not validate the Host header, enabling a web page that rebinds its domain to the loopback address to perform same-origin requests and access sensitive path information. This exposure can reveal local usernames and project layout details.
CVE-2026-117510 is a path traversal vulnerability in Dexmal Dexbotic versions 0.1 and 0.2.0. It affects the load_pretrained_gr00t function in the gr00tsonic Checkpoint Loader component. The flaw allows remote attackers to manipulate the weight_map argument to perform path traversal. Exploit code has been published, but no vendor response or patch is currently available.
Authlib versions 1.6.0 through before 1.9.0 contain a vulnerability in the RFC 9101 JAR extension where the attacker-controlled request_uri parameter is passed to a fetch hook without validation at a pre-authentication endpoint. This allows an unauthenticated Server-Side Request Forgery (SSRF) primitive because the documented example implementation performs an unrestricted HTTP GET on the request_uri. The vulnerability arises because the existing allowlist controls for request_uris are ignored, and the extension does not implement required RFC 9101 controls such as validating the URI location, media type, or timeouts. A fix is available in version 1.9.0.
Authlib versions prior to 1.9.0 contain a vulnerability in the OpenID ID token nonce validation process. The ID token's nonce validation can be disabled if the token includes a boolean false nonce_supported claim, causing the expected nonce to be set to None and skipping nonce validation. This allows an attacker to replay a validly signed ID token from a victim into an attacker-controlled session, authenticating as the victim. The vulnerability affects implicit and hybrid flows and direct calls to parse_id_token(), but not the authorization code flow. A fix is available in version 1.9.0.
Authlib versions prior to 1.9.0 have a vulnerability in the default JWT bearer grant implementation where the audience ('aud') claim in JWT assertions is not properly validated. The default get_audiences() method returns an empty list, causing verify_claims() to only check for the presence of an 'aud' claim rather than verifying it matches the authorization server's token endpoint. This allows an attacker with a valid JWT for any audience to obtain an access token from a different authorization server sharing the same signing key.
Authlib versions prior to 1.9.0 contain a vulnerability in the OpenID Connect implicit grant implementation where the authorization request's raw scope parameter is checked instead of the filtered allowed scope. This allows a registered OAuth client, which is not permitted the 'openid' scope but allowed other scopes like 'profile', to obtain a signed ID token if the user consents. The ID token includes identity claims such as 'sub' and 'name', effectively bypassing intended scope restrictions. The issue is fixed in version 1.9.0.
Authlib versions from 1.3.1 up to but not including 1.9.0 contain a vulnerability in the handling of HMAC keys in the jose module. The check that prevents asymmetric public keys from being used as HMAC secrets only inspects the start of the key bytes, but the asymmetric key loader skips leading bytes before the PEM header. This discrepancy allows an attacker with only the issuer's public key to craft a valid HS256 token with arbitrary claims that will be accepted as authentic. The issue is an incomplete fix of a previous vulnerability (CVE-2024-37568) and affects the documented usage of the jwt.decode method. A fix is available in version 1.9.0.