Search Results (3344 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2026-82948 1 Onyx Cookware Aps 1 Nexsmart Guardian 2 (alarm System) 2026-11-21 N/A
The Guardian 2 alarm unit lacks a mechanism to authenticate control commands sent over 433.92 MHz, which allows an attacker to replay the static commands to impersonate activity.  The attacker can also disarm or arm the system at will if a Nexsmart keypad (product link) is in use, thus compromising the functionality of the alarm system completely.
CVE-2026-86587 1 Ezviz 1 Certain Ezviz Devices 2026-11-21 5.3 Medium
Certain EZVIZ devices are affected by an improper certificate validation issue (CWE-295). An attacker may intercept communication traffic to conduct a man-in-the-middle attack.
CVE-2026-86586 1 Ezviz 5 Cs-c6n-b0-1g2wf, Cs-c6n-r101-1g2wf, Cs-h7c-r101-8h44wf and 2 more 2026-11-21 4.2 Medium
Certain EZVIZ devices are affected by a replay attack vulnerability (CWE-294). An attacker may intercept communication traffic and replay specific control commands, causing the device to execute unauthorized operations.
CVE-2026-125273 1 Elecbrakes 3 Eb2, Elbc2000, Vm1 2026-11-21 9.6 Critical
No replay or command-integrity protection. Commands lack sequence numbers, nonces, or session tokens; captured commands can be replayed, and the last command persists across sessions.
CVE-2026-133949 1 Pip Maintainers 1 Pip 2026-11-21 N/A
pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.  Upgrading to a secure version of pip should be done either by first upgrading Python to a version that rejects the compromised intermediates (CVE-2026-115557) or use hash pinning with a known-secure version of pip. pip is not vulnerable when using a Python version that rejects the compromised certificates. See the references below for more information.
CVE-2026-134276 1 Vikunja 1 Vikunja 2026-11-21 3.7 Low
Vikunja from 2.2.1 before 2.8.0 contains a TOTP replay protection bypass in ValidateTOTPPasscode that allows attackers to reuse consumed codes by padding them with whitespace. Attackers with valid credentials who observe a used passcode can resubmit it whitespace-padded to the login API within the validity window to obtain a session token.
CVE-2026-75521 1 Mirendev 1 Runtime 2026-11-21 N/A
Miren Runtime provides the runtime component for the Miren application platform. Prior to 0.11.1, the QUIC/HTTP3 RPC server on the default port 8443 uses tls.RequestClientCert and does not verify that presented certificates chain to the configured cluster certificate authority. The RPC authenticators derive a caller identity from PeerCertificates[0].Subject.CommonName without requiring a non-empty VerifiedChains value, and certificate identities bypass all RBAC checks. A network attacker who can reach the listener can present a self-signed certificate with an issuer distinguished name matching the public cluster CA subject and gain cluster superuser access, allowing disclosure, modification, or disruption of applications, sandboxes, disks, credentials, and other managed resources. This issue is fixed in version 0.11.1.
CVE-2026-132934 1 Jetbrains 1 Teamcity 2026-11-21 5.9 Medium
In JetBrains TeamCity before 2026.2, 2026.1.4 authentication bypass via polling agent name rebinding was possible
CVE-2026-132987 1 Jetbrains 1 Teamcity 2026-11-21 4.8 Medium
In JetBrains TeamCity before 2026.2 server certificates were not verified in the SVN integration
CVE-2026-63012 1 Baserproject 1 Basercms 2026-11-21 6.5 Medium
baserCMS is a website development framework. Prior to 5.3.0, getAuthenticationService permits an Api/Admin session authentication fallback based on the Referer header, although operator accounts have an Admin auth prefix and cannot obtain an Api/Admin JWT. An authenticated operator can therefore access /baser/api/admin/ endpoints whose permission.php entries have auth => true, including /baser/api/admin/baser-core/site_configs/view.json, even when the corresponding administrative functionality is restricted. This can disclose administrator-restricted configuration information. This issue is fixed in 5.3.0.
CVE-2026-61832 1 Nukeviet 1 Nukeviet 2026-11-21 7.5 High
NukeViet CMS is a multi Content Management System. Prior to 4.6.00, a network attacker who can alter outbound traffic to the extension store can exploit the HTTP client's disabled sslverify setting to substitute a serialized response. Extension-store handlers pass the response to unserialize() without an allowed_classes restriction, allowing an in-tree GuzzleHttp\Cookie\FileCookieJar gadget to write attacker-controlled content to a chosen path. When a GODADMIN opens or uses the store list, detail, install, or update functions, the substituted response can write a PHP file under the web root and execute code as the web-server user. This issue is fixed in version 4.6.00.
CVE-2026-133180 1 Jetbrains 1 Resharper 2026-11-21 3.7 Low
In JetBrains ReSharper before 2026.3 the What's New feature did not verify server certificates
CVE-2026-44908 2026-11-21 4.8 Medium
Improper following of a certificate’s chain of trust in the remote-attestation verifier used to establish trust with Meta AI's confidential computing backend in WhatsApp for iOS before 2.26.24.72, WhatsApp Business for iOS and WhatsApp for Mac Desktop before v2.26.23.72, WhatsApp for Android before v2.26.23.74, and WhatsApp Business for Android before v2.26.23.70 could have allowed someone positioned within Meta infrastructure to bypass the hardware root of trust by presenting clients with a VCEK certificate signed by a key other than the hardware manufacturer’s. Any such VCEK Cert would first have to be published to the third-party binary transparency ledger used by WhatsApp Private Processing. The ledger shows that every published VCEK certificate chains to the hardware root of trust, confirming no exploitation.
CVE-2026-133477 1 Sofastack 1 Sofa-bolt 2026-11-21 3.7 Low
A weakness has been identified in sofastack sofa-bolt up to 1.6.12. This impacts the function initSSLContext of the file src/main/java/com/alipay/remoting/connection/AbstractConnectionFactory.java of the component TLS Stack. Executing a manipulation can lead to certificate with host mismatch. The attack may be performed from remote. This attack is characterized by high complexity. The exploitability is said to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-133648 1 Flowintel 1 Flowintel 2026-11-21 N/A
Flowintel disabled TLS certificate verification for all MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This allowed an on-path (man-in-the-middle) attacker positioned between Flowintel and its MISP or mail servers to impersonate the remote server and intercept sensitive data. Affected connections include: - All MISP HTTPS API calls (event retrieval, attribute search, event creation, connectivity checks, and API validation) - SMTP STARTTLS connections used for sending email notifications - IMAP TLS connections used for fetching mail archives and testing connectivity An attacker who can observe or intercept network traffic between Flowintel and the MISP or mail server could: - Capture MISP API keys and mail credentials (SMTP/IMAP passwords) - Read all threat intelligence data exchanged (events, attributes, objects, reports) - Inject or modify threat intelligence data returned to Flowintel The vulnerability required no authentication on the part of the attacker and no user interaction; it was exploitable by any party with a network position between Flowintel and its configured MISP or mail endpoints. Affected versions: Flowintel prior to 4.1.0.
CVE-2026-133853 1 Flowintel 1 Flowintel 2026-11-21 N/A
FlowIntel's chatbot component used a single shared MCP (Model Context Protocol) session and process-wide environment variable to pass per-user API credentials to a child process. Because the session and the ambient FLOWINTEL_API_KEY environment variable were shared across all concurrent requests, a user's authenticated identity could be applied to another user's tool invocation, or a stale/ambient credential could be inherited by a new request. Preconditions: - An authenticated user with access to the chatbot interface. - Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user's credentials were written to the process environment. Impact: - A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases). - A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential. - The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface. Affected versions: FlowIntel prior to 4.1.0.
CVE-2026-133181 1 Jetbrains 2 Resharper, Rider 2026-11-21 3.7 Low
In JetBrains ReSharper before 2026.3 server host names were not verified during certificate validation
CVE-2026-129509 1 Apache 1 Airflow Microsoft Azure Provider 2026-11-21 7.5 High
In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, `S3ToAzureBlobStorageOperator` turned off TLS certificate verification for its connection to Amazon S3 by default (`s3_verify=False`), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses `S3ToAzureBlobStorageOperator` without setting `s3_verify`. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default.
CVE-2026-129705 1 Eclipse 1 Eclipse Mosquitto 2026-11-21 9.1 Critical
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, a broker with a listener that is configured to use the PROXY protocol v2 is vulnerable to an untrusted proxy providing details that cause the broker to accept fake SSL information. This can be mitigated by following the documented requirements for PROXY listeners: It is very important that only trusted proxies are allowed to connect to any listener using the PROXY protocol, and that clients are not allowed to connect to the listener at all.
CVE-2026-130756 1 Pnpm 1 Exe 2026-11-21 9.8 Critical
pnpm exe before 10.34.8 embeds an outdated Node.js runtime that still trusts compromised eMudhra intermediate CA certificates during registry TLS connections. Network attackers holding a recovered intermediate key can intercept standalone pnpm registry fetches and serve forged package metadata or tarballs.