Mattermost Desktop App versions <=6.3 6.0.3 6.3.2.0 fail to validate the SiteURL value returned in a server's client configuration before constructing a server object from it which allows an operator of a server configured in the Desktop app to render the application persistently unusable across restarts via an unparseable SiteURL that triggers an uncaught exception reaching the process-level critical error handler. Mattermost Advisory ID: MMSA-2026-00770
NVIDIA Transformer Engine for Linux contains a vulnerability where a user could cause deserialization by loading untrusted data. A successful exploit of this vulnerability might lead to code execution, information disclosure, and denial of service.
ICRTouch TouchTakeaway versions 1 through 2 are affected by a Cross-Site Request Forgery (CSRF) vulnerability due to inconsistent implementation of anti-CSRF protections. This flaw allows an attacker to trick an authenticated user into submitting unauthorized state-changing requests without verifying the request's origin.
ICRTouch TouchTakeaway versions 1 through 2 contain an authorization bypass vulnerability in the order-tracking functionality. This flaw allows an unauthenticated remote attacker to modify order identifiers and access information related to other customers' orders without proper authorization checks.
ICRTouch PocketTouch version 1.700 build 2025.3726 contains a hard-coded default socket password set to the literal value 'password'. If this default password is not changed and is accepted by a TouchPoint POS terminal, an attacker with network access to the terminal's socket service may authenticate using these publicly known credentials.
CVE-2026-122141 is a Cross-Site Request Forgery (CSRF) vulnerability in the wallet top-up functionality of ICRTouch TouchTakeaway and ByTable products. The flaw allows an attacker-controlled website to cause an authenticated customer's browser to submit unauthorized wallet top-up requests, adding attacker-selected charges to the customer's active cart.
ICRTouch Commander versions 1 through 2 have an authentication vulnerability where the administrative login interface does not properly limit repeated login attempts. Additionally, the interface reveals different responses based on authentication states and the presence of a siteID parameter, potentially aiding attackers in enumerating valid credentials or sites.
ICRTouch Commander has a vulnerability where its administrative interface uses HTTP GET requests for security-sensitive operations and includes an API key in the URL query string. This practice risks exposing the API key through browser history, logs, analytics, and referrer headers.
ICRTouch PocketTouch version 1.700 build 2025.3726 transmits the POS socket password in plaintext XML over an unencrypted TCP connection. This lack of transport-layer encryption allows an attacker who can observe network traffic between a PocketTouch device and a TouchPoint POS terminal to capture and recover the socket password.
ICRTouch PocketTouch version 1.700 build 2025.3726 contains hard-coded default credentials in multiple fields, including socket, configuration, and shutdown passwords. An email-related password field is also initialized but left empty. This use of hard-coded credentials can lead to unauthorized access if these defaults are not changed.
CVE-2026-122149 is a vulnerability in ICRTouch TouchPoint POS where the SAVECONFIG command can be used by an attacker with network access to overwrite till configuration files remotely. This flaw stems from missing authentication for critical functionality, allowing unauthorized modification of terminal configuration data.
CVE-2026-122150 is an authentication vulnerability in ICRTouch TouchPoint POS affecting the CHECKPAYMENT workflow. The system accepts a caller-supplied clerk number without properly verifying authorization, allowing an attacker with POS protocol access to impersonate another employee and submit payment requests under that identity.
CVE-2026-122153 is a vulnerability in the ICRTouch TouchOffice API where the clerkList endpoint exposes sensitive authentication data such as clerk PINs and iButton serial numbers to unauthorized callers. This exposure allows access to reusable authentication credentials beyond what is necessary for listing clerks.
The ICRTouch TouchTakeaway Cordova applications do not implement certificate or public-key pinning for backend HTTPS connections, relying solely on the device's system trust store for server certificate validation. This improper certificate validation could allow an attacker who controls a trusted certificate authority or uses a compromised certificate to intercept and modify application traffic.
Device code phishing is a social engineering attack where an attacker initiates an OAuth device flow sign-in request and persuades a user to approve it, granting access to the attacker. This technique was demonstrated in a controlled simulation targeting GitHub Copilot CLI, an AI coding agent that uses OAuth device flow for authentication. Approval of the device code by the user can allow an attacker to remotely control active Copilot CLI sessions, manipulate the agent's memory, read synchronized sessions, and access private repositories. These outcomes depend on user permissions and enabled features. The attack leverages legitimate OAuth flows and does not involve password theft. Microsoft Defender can detect such attacks by correlating phishing attempts with GitHub authentication activity. The technique is not specific to GitHub and can affect any public client supporting OAuth device flow.
French market research company Ipsos disclosed a breach of one of its internal information systems. The incident was made public on November 16, 2026, five days after the company filed a complaint with authorities. Ipsos reported no disruption to its business operations and stated that the investigation is ongoing to determine the nature and scope of the breach. The company has not confirmed whether any data was accessed or stolen and has not provided details on the affected system or attack vector. Ipsos emphasized its commitment to protecting entrusted information and will notify affected parties if client, project, or partner data is impacted.
A vulnerability in react-native-webview versions 13.7.0 through 17.1.0 on Windows allows malicious web content to launch Windows protocol handlers without user confirmation. This occurs because the WebView2 OnCoreWebView2NewWindowRequested handler passes requested URIs to LaunchUriAsync without validating the URI scheme or requiring user initiation. Attackers can exploit this by using window.open() or target=_blank links with schemes like ms-settings: to bypass the external-protocol confirmation prompt.
react-native-webview versions 13.8.0 through 17.1.0 have a code injection vulnerability. This flaw allows attackers to execute arbitrary JavaScript by injecting unescaped backticks or ${} sequences into injectedJavaScriptObject string values. Exploitation could enable access to the page DOM, non-HttpOnly cookies, and the ReactNativeWebView message bridge.
GPAC versions from 26.02.0 up to but not including 26.07.0 contain a NULL pointer dereference vulnerability in the dasher_configure_pid() function. This flaw occurs because the code dereferences a pointer without checking if it is NULL, leading to a crash when processing crafted MPEG-2 TS files with MP4Box -dash. Successful exploitation results in a denial of service by crashing the MP4Box tool.
GPAC versions prior to 26.07.0 contain a vulnerability where an uninitialized pointer is accessed in the GetESD() function within src/isomedia/track.c. This flaw can be triggered by a crafted MP4 file containing an rvcc box with predefined_rvc_config set to 0 and lacking a meta item index, leading to a crash of the MP4Box -add utility due to invalid memory reads.