Before 4.92.0, Docker Desktop for Windows did not verify the signature of a package supplied to Docker Desktop Installer.exe install -package. An attacker able to provide a crafted package and convince a user to approve the Docker-signed UAC prompt could execute attacker-controlled installer actions as LocalSystem.
CVE-2026-86405 is a critical vulnerability in the Sipay Electronic Money and Payment Services Inc. PrestaShop Virtual POS Module. It involves improper verification of cryptographic signatures, allowing signature spoofing due to improper validation. This affects versions from 26.8.1 up to but not including 26.9.1. The vulnerability has a high CVSS score of 9.8, indicating severe impact on confidentiality, integrity, and availability.
CVE-2026-85531 is a critical vulnerability in the OpenCart Virtual POS Module by Sipay Electronic Money and Payment Services Inc. It involves improper verification of cryptographic signatures, allowing signature spoofing due to improper validation. This affects versions from 26.8.2 up to but not including 26.9.1.
The Super Payments WordPress plugin before 1.43.1 does not properly verify the authenticity of incoming payment webhook notifications, as the signing key used to validate their signature is empty by default, allowing unauthenticated attackers to forge a valid signature and mark arbitrary WooCommerce orders as paid without payment.
fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.2.4, fast-jwt can classify raw serialized public JWK or JWKS JSON as an HMAC secret because src/crypto.js performDetectPublicKeyAlgorithms treats non-PEM strings as symmetric key material. If HS256 is explicitly allowed or inferred, an attacker who knows the exact serialized public-key bytes can use those bytes as an HMAC key and create a token containing arbitrary claims that createVerifier accepts. Serialization ordering or whitespace differences can prevent exploitation, and applications using supported PEM keys with an asymmetric-only algorithm allowlist are not affected. This issue is fixed in version 6.3.0.
fast-jwt versions from 6.2.0 up to but not including 6.3.0 contain a vulnerability where RSA public keys with non-whitespace content before the PEM header are misclassified as HMAC secrets. This misclassification allows an attacker who knows the public key bytes to forge HS256 signatures, potentially bypassing authentication or authorization. The issue is resolved in version 6.3.0.
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.1, fast-jwt createVerifier accepts an unsigned JWT when key is an empty string or null and algorithms is a non-empty allowlist. Falsy synchronous keys bypass prepareKeyOrSecret, allowedAlgorithms remains active, hasKey is false, and the empty signature avoids the verifySignature gate. An attacker can therefore submit a token containing arbitrary claims without possessing a signing key, resulting in authentication or authorization bypass. Claim validators still run, and non-empty keys, an empty key without algorithms, and the async key resolver path do not have this behavior. This issue is fixed in version 6.3.1.
CVE-2026-14497 is a high-severity vulnerability in IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. It involves improper verification of cryptographic signatures that could allow a remote authenticated attacker to bypass security restrictions. The vulnerability has a CVSS 3.1 score of 8.1, indicating a significant impact on confidentiality and integrity without affecting availability. No information about available patches or vendor advisories is provided, so patch status is not confirmed.
IBM DataPower Gateway versions 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 contain a vulnerability that allows remote attackers to bypass authentication by forging valid JSON Web Signatures. This occurs due to improper verification of cryptographic signatures, classified under CWE-347. The vulnerability has a high severity with a CVSS score of 7.4.
Cryptographic Issue when processing non-ELF partitions, authentication and signature checks are bypassed, allowing unsigned or corrupted images to be mounted and processed.
In Progress® Telerik® Fiddler® Classic for Windows, versions prior to v6.0.20262.10021, the integrity check applied to the external helper tools launched by the application is insufficient. Before executing a helper tool, the application only verifies that the file carries a valid Authenticode signature whose certificate subject name matches a broad allow list of publisher name fragments, rather than verifying that the file is the specific executable shipped with that version of the product. A local threat actor with low privileges who replaces one of these helper executables with any other validly signed binary from an allow-listed publisher can cause the substituted binary to be executed by the application, including with Administrator privileges for the tools that request elevation, resulting in privilege escalation and execution of unintended code. Successful exploitation requires the user to launch the affected external tool and to approve the elevation prompt without noticing that it refers to a different executable.
CVE-2026-71891 is a cryptographic signature verification vulnerability in Bouncy Castle for Java versions 1.85 up to but not including 1.86. The flaw allows acceptance of a public key constructed on a non-canonical elliptic curve that mimics the BLS12-381 curve's field characteristic but is not valid. This leads to improper subgroup validation, enabling an aggregate signature to be accepted even when it contains a phantom signer. The issue only occurs if an application explicitly constructs ECPoints on non-standard curves; the default compressed-point decoder is unaffected. The vulnerability is fixed in version 1.86.
CVE-2026-71887 is a vulnerability in Bouncy Castle for Java (BC-JAVA) versions 1.81 up to but not including 1.86. The high-level OpenPGP API improperly verifies cryptographic signatures by accepting a signing subkey that lacks the required embedded Primary Key Binding signature in its Subkey Binding signature, violating RFC 9580 requirements. This flaw allows an attacker to misattribute a genuine signature made by the victim's public signing subkey to an attacker-chosen identity, without forging a new signature or recovering private keys. The issue is fixed in version 1.86.
An improper verification of cryptographic signature vulnerability exists in protocol gateways because the device does not properly verify the cryptographic authenticity of firmware images before installation. An attacker with high privileges and access to the firmware update interface could provide a specially crafted or modified firmware image, causing it to be installed on the device. Successful exploitation could allow the attacker to execute unauthorized code, compromise the integrity and availability of the device, and persist malicious modifications across subsequent firmware updates.
CVE-2026-63571 is a high-severity vulnerability in Legion of the Bouncy Castle Inc.'s bc-csharp library before version 2.7.0. It involves improper verification of cryptographic signatures in the attribute certificate path validator, allowing a remote attacker to forge X.509 attribute certificates. This flaw permits acceptance of forged certificates that name a trusted attribute authority as issuer but are not actually signed by it. Only applications using these specific classes for attribute certificate validation are affected.
CVE-2026-18397 is a critical vulnerability in Thales SConnect native host component that allows unauthenticated remote code execution. It arises from improper verification of cryptographic signatures combined with memory management issues. The vulnerability exploits an unrestricted messaging interface between attacker-controlled web pages and the native host, enabling malicious input to bypass security checks. This affects versions prior to 2.16.1.0.
Improper verification of cryptographic signature vulnerability in Apache APISIX.
Any unauthenticated attacker could impersonate any user on every route protected by the saml-auth plugin under default configuration. This issue affects Apache APISIX: from 3.17.0 through 3.18.0.
Users are recommended to upgrade to version 3.19.0, which fixes the issue.
Tugtainer is a self-hosted app for automating updates of Docker containers. Prior to version 1.31.3, when the OIDC login flow completes, backend/modules/auth/providers/auth_oidc_provider.py decodes the id_token returned by the identity provider's token endpoint using jose.jwt.get_unverified_claims() instead of jwt.decode(). This skips signature verification, audience (aud) validation, issuer (iss) validation, and expiry (exp) checking entirely. The extracted claims (email/sub/preferred_username) are then used directly as the user_id for the resulting Tugtainer session. This issue has been patched in version 1.31.3.