Export limit exceeded: 428340 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (428340 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-130603 | 1 Eclipse | 1 Eclipse Zenoh | 2026-11-18 | N/A |
| Eclipse Zenoh's zenoh-pico implementation, versions 0.7.2-rc up to but excluding 1.10.2, does not validate the Zenoh identifier (ZID) length when deserializing timestamps. An attacker-controlled length greater than 16 causes an out-of-bounds write to a fixed 16-byte identifier buffer and causes the subsequent zero-fill operation to receive a negative length converted to a large unsigned size. Truncated timestamp inputs can also cause out-of-bounds reads or assertion failures. A remote attacker able to deliver crafted timestamp-bearing Zenoh messages through an accepted transport can cause memory corruption and denial of service, with potential remote code execution in builds lacking appropriate binary protections. This issue is fixed in version 1.10.2. Depending on the release and message-decoding path, the unchecked timestamp identifier length causes a heap-based or stack-based buffer overflow. Ordinary-frame network message decoding moved from heap-backed storage to stack-local storage in version 1.5.0. Earlier affected releases already contained stack-based decoding paths, including reassembled fragmented messages. | ||||
| CVE-2026-130626 | 1 A2a-java | 1 A2a-java-sdk-http-client | 2026-11-18 | 7.5 High |
| The core JDK HTTP client (a2a-java-sdk-http-client) applies the GHSA-9rhm redirect-neutralization only to the POST path. JdkGetBuilder.get(), JdkGetBuilder.getAsyncSSE(), and JdkDeleteBuilder.delete() call the injected httpClient directly, with no redirect gate. An application that supplies a redirect-capable HttpClient (Redirect.NORMAL/ALWAYS) — which is the SDK-documented way to enable POST redirects — silently follows cross-authority redirects on every credentialed GET/DELETE request. The JDK strips Authorization cross-origin, but forwards the four allowlisted custom credential headers (X-API-Key, API-Key, X-Auth-Token, X-Authentication) to the attacker-controlled authority. This is an incomplete-fix variant of GHSA-9rhm: the fix hardened the default client and added a POST-only two-step opt-in, but never covered GET/DELETE. | ||||
| CVE-2026-118789 | 1 Cipcarbone | 1 Farmasimplex | 2026-11-18 | N/A |
| Farmasimplex retrieves a CIP News file over HTTP and executes embedded SQL statements against the local FarmaCIP database with administrative privileges. An attacker able to tamper with network communications or compromise vendor infrastructure can inject arbitrary SQL commands, leading to unauthorized access to, modification or deletion of database contents and potentially operating system command execution. | ||||
| CVE-2026-130627 | 1 A2a-java | 1 A2a-java-sdk-http-client-vertx | 2026-11-18 | 7.5 High |
| The Vert.x HTTP client transport (a2a-java-sdk-http-client-vertx) hand-rolls a POST redirect follower that, when the documented PostBuilder.followRedirects(true) opt-in is enabled, re-issues the redirected request with the full request header map copied verbatim and performs no credential stripping and no same-authority check. A malicious, compromised, or mistyped agent that returns a 30x response with an absolute cross-host Location causes the client to forward the standard Authorization header (Bearer/Basic/OAuth) — plus every other header, including the allowlisted API-key headers — to the attacker-controlled authority. This breaks the project's own cross-transport invariant (SECURITY.md §8, OkHttpPostRedirectHeaderLeakTest) that credentials are stripped on cross-authority redirects even when redirects are followed. The sibling JDK and OkHttp/Android transports strip Authorization; Vert.x uniquely does not. This is a "fix introduced the bug" variant — the follower was added by the GHSA-9rhm hardening PR (3ae82912, refined by a5e76a0b). | ||||
| CVE-2026-123050 | 1 Cipcarbone | 1 Farmasimplex | 2026-11-18 | N/A |
| Multiple Farmasimplex healthcare integration modules do not properly validate TLS certificates, allowing an attacker who can intercept network traffic to impersonate trusted healthcare services and perform man-in-the-middle attacks, potentially leading to disclosure or modification of sensitive data. | ||||
| CVE-2026-123051 | 1 Cipcarbone Srl | 1 Farmasimplex Rev.exe | 2026-11-18 | N/A |
| The REV.exe module distributed with Farmasimplex contains embedded OAuth client credentials for integration with the IZS platform. An attacker with access to the executable could extract and reuse the credentials, potentially leading to unauthorized access to integration resources or manipulation of associated information, depending on the privileges granted and authentication controls in place. | ||||
| CVE-2026-123052 | 1 Cipcarbone | 1 Farmasimplex Celiachiarl | 2026-11-18 | N/A |
| The CeliachiaRL integration component distributed with Farmasimplex uses shared OAuth credentials across multiple customer installations. An attacker who obtains the credentials from one installation could reuse them against services associated with other installations, potentially leading to unauthorized access to sensitive information or modification of integration data. | ||||
| CVE-2026-130629 | 1 React-native-webview | 1 React-native-webview | 2026-11-18 | 4.7 Medium |
| react-native-webview 13.8.0 through 17.1.0 contains a code injection vulnerability that allows attackers to execute JavaScript by placing unescaped backticks or ${} sequences in injectedJavaScriptObject string values. Attackers who control values like profile fields or API responses can break out of the template literal to access the page DOM, non-HttpOnly cookies, and the ReactNativeWebView message bridge. | ||||
| CVE-2026-130628 | 1 React-native-webview | 1 React-native-webview | 2026-11-18 | 4.3 Medium |
| react-native-webview 13.7.0 through 17.1.0 on Windows contains an unrestricted URI scheme launch vulnerability in the WebView2 OnCoreWebView2NewWindowRequested handler, which passes requested URIs to LaunchUriAsync without scheme or user-initiation checks. Malicious web content can call window.open() or use target=_blank links with schemes like ms-settings: to launch Windows protocol handlers without the external-protocol confirmation prompt. | ||||
| CVE-2026-122152 | 1 Icrtouch | 1 Touchtakeaway | 2026-11-18 | 5.9 Medium |
| The ICRTouch white-label TouchTakeaway Cordova applications do not implement certificate or public-key pinning for backend HTTPS connections. The applications therefore rely exclusively on the device’s system trust store when validating server certificates. An attacker who can cause a device to trust an attacker-controlled certificate authority, or who operates through a compromised or improperly issued trusted certificate, may be able to intercept and modify application traffic. | ||||
| CVE-2026-122153 | 1 Icrtouch | 1 Touchoffice | 2026-11-18 | 7.5 High |
| The TouchOffice API `clerkList` endpoint appears to return sensitive clerk authentication data, including clerk PINs and iButton serial numbers. If the endpoint is accessible to callers who do not require access to these values, the API exposes reusable authentication material beyond the minimum information necessary for clerk-list functionality. | ||||
| CVE-2026-122150 | 1 Icrtouch | 2 Pockettouch, Touchpoint Pos | 2026-11-18 | 9.1 Critical |
| The PocketTouch and TouchPoint POS `CHECKPAYMENT` workflow accepts a caller-supplied clerk number without adequately verifying that the requesting client is authorized to act as that clerk. An attacker with access to the POS protocol may be able to specify another employee’s clerk identifier and submit payment-related requests under that identity. | ||||
| CVE-2026-122149 | 1 Icrtouch | 2 Pockettouch, Touchpoint Pos | 2026-11-18 | 9.1 Critical |
| The PocketTouch and TouchPoint POS protocol includes a `SAVECONFIG` command that appears capable of overwriting till configuration files remotely. An attacker with network access to the POS socket service may be able to submit a crafted `SAVECONFIG` command and replace or modify terminal configuration data. | ||||
| CVE-2026-122147 | 1 Icrtouch | 1 Pockettouch | 2026-11-18 | 9.8 Critical |
| ICRTouch PocketTouch version 1.700 build 2025.3726 defines hard-coded default values for multiple credential fields, including a socket password and configuration and shutdown passwords. An additional email-related password field is initialized without a value. | ||||
| CVE-2026-122145 | 1 Icrtouch | 1 Pockettouch | 2026-11-18 | 7.5 High |
| ICRTouch PocketTouch version 1.700 build 2025.3726 transmits the POS socket password in plaintext XML over an unencrypted TCP connection. The protocol does not provide transport-layer encryption to protect credentials from interception. An attacker able to observe network traffic between a PocketTouch device and a TouchPoint POS terminal can recover the socket password from captured packets. | ||||
| CVE-2026-122143 | 1 Icrtouch | 1 Commander | 2026-11-18 | 7.5 High |
| ICRTouch Commander administrative interface performs security-sensitive operations through HTTP GET requests and includes an API key in the request query string. GET requests are commonly retained in browser history, proxy logs, server logs, analytics systems, referrer headers, and other intermediary records. | ||||
| CVE-2026-122142 | 1 Icrtouch | 1 Commander | 2026-11-18 | 9.8 Critical |
| ICRTouch Commander administrative login interface does not adequately restrict repeated authentication attempts. The interface also returns distinguishable responses for multiple authentication states, including different behavior when a `siteID` value is supplied. | ||||
| CVE-2026-122141 | 1 Icrtouch | 2 Bytable, Touchtakeaway | 2026-11-18 | 8.1 High |
| The wallet top-up functionality in ICRTouch ByTable and TouchTakeaway does not adequately protect state-changing requests against CSRF. An attacker-controlled website can cause an authenticated customer’s browser to submit a wallet top-up request and add an attacker-selected charge to the customer’s active cart. | ||||
| CVE-2026-122055 | 1 Icrtouch | 1 Pockettouch | 2026-11-18 | 9.8 Critical |
| ICRTouch PocketTouch version 1.700 build 2025.3726 contains a default socket password set to the literal value password. Where the default value remains unchanged and is accepted by a TouchPoint POS terminal, an attacker with network access to the terminal’s socket service may authenticate using publicly known credentials. | ||||
| CVE-2026-122122 | 1 Icrtouch | 2 Bytable, Touchtakeaway | 2026-11-18 | 9.1 Critical |
| The order-tracking functionality in ICRTouch ByTable and TouchTakeaway does not adequately verify that a requester is authorized to access the specified order. An unauthenticated remote attacker can modify an order identifier to retrieve information associated with other customers’ orders. | ||||