PULSE
FEED
ransomnetrunner reclama a Instant Access · KW · Technologyransomcurious worm reclama a ex********s.comransomaoqin reclama a Anmat Technology for Trading Co. · SA · Otherransomcurious worm reclama a risingpharma.com · US · Healthcareransomqilin reclama a Strategic Properties · USransomqilin reclama a The Ashland Water Group · US · Energy & Utilitiesransomqilin reclama a The National Commission on Indigenous Peoples · PH · Government & Defenseransomchaos reclama a radienzliving.com · DE · Retail & E-Commerceransomchaos reclama a amarok.com · Technologyransomvortex reclama a APELLIS · US · Healthcareransomglobal secret group reclama a Johnson Bros. Bakery Supply, Inc. · US · Agriculture and Food Productionransomcurious worm reclama a t**l**kw*****p.com · Technologyransomqilin reclama a Airways Aviation · AE · Transportationransomqilin reclama a Ayala Property Management · PH · Otherransomnetrunner reclama a Instant Access · KW · Technologyransomcurious worm reclama a ex********s.comransomaoqin reclama a Anmat Technology for Trading Co. · SA · Otherransomcurious worm reclama a risingpharma.com · US · Healthcareransomqilin reclama a Strategic Properties · USransomqilin reclama a The Ashland Water Group · US · Energy & Utilitiesransomqilin reclama a The National Commission on Indigenous Peoples · PH · Government & Defenseransomchaos reclama a radienzliving.com · DE · Retail & E-Commerceransomchaos reclama a amarok.com · Technologyransomvortex reclama a APELLIS · US · Healthcareransomglobal secret group reclama a Johnson Bros. Bakery Supply, Inc. · US · Agriculture and Food Productionransomcurious worm reclama a t**l**kw*****p.com · Technologyransomqilin reclama a Airways Aviation · AE · Transportationransomqilin reclama a Ayala Property Management · PH · Other
← Todos los CVEs
CVE Watch16 nov 2026

CVE-2026-93673

The Zephyr WebSocket client validates the server's handshake response in on_header_value() in subsys/net/lib/websocket/websocket.c. The comp

CVSS

4.8

Medio

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 16 nov 2026 · Última mod.: 16 nov 2026 · CWE-345

EPSS · 30d

Sin historial EPSS suficiente todavía.

Descripción técnica

The Zephyr WebSocket client validates the server's handshake response in on_header_value() in subsys/net/lib/websocket/websocket.c. The comparison was performed as strncmp(at, str, length), where length is the length of the value the server sent rather than the length of the expected value, so the check only asked whether the received value was a prefix of the expected base64(SHA-1(key || GUID)). A server that returned a handful of correct characters passed, and a response carrying an empty Sec-WebSocket-Accept: header caused strncmp() to be called with a count of zero, which returns 0 and set ctx->sec_accept_ok with no comparison performed at all. The header-value callback also cleared ctx->sec_accept_present after the first chunk, so a value split across receive-buffer boundaries was only ever examined in part. ctx->sec_accept_ok is the sole WebSocket-specific gate in websocket_connect(); the client does not check the HTTP status code or the Upgrade:/Connection: headers. Any HTTP response containing an empty or prefix-matching Sec-WebSocket-Accept header therefore completed the handshake, after which the socket is finalized as a WebSocket and all further peer bytes are parsed as frames. The affected path is driven directly by remote input through subsys/net/lib/http/http_parser.c, and is reached by every user of websocket_connect(), including MQTT over WebSocket (subsys/net/lib/mqtt/mqtt_transport_websocket.c) and subsys/net/lib/ocpp/ocpp.c. The Sec-WebSocket-Accept exchange is not a secret-based authentication -- an endpoint or on-path attacker that sees the request can compute the expected value -- so the impact is bounded to parties that never observed the handshake request: a caching or transparent intermediary replaying a canned response, an off-path attacker injecting a spoofed response, or a non-WebSocket endpoint the client was induced to talk to. For those, the per-connection binding that RFC 6455 requires the client to enforce provided no protection at all, letting a single crafted response convince the device it holds a live WebSocket session and causing it to send application data to, and accept frames from, an unverified peer. There is no memory-safety consequence. The fix compares each delivered chunk against the expected value at the position reached so far, refuses a chunk that would overrun it, and accepts only once every byte of the expected value -- and no more -- has been matched; on_header_field() now also clears the flag for any other header so a partial value cannot be continued across an intervening header.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1155637.5 ALT
—
———The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.9.1 until 1.30.0 and 2.2.0, OAuth client support in mcp.client.auth can send credentials to an authorization server chosen by an untrusted MCP server. ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider cannot identify the authorization server that owns their credentials. Affected HTTP clients using those providers, OAuthClientProvider, or the deprecated 1.x RFC7523OAuthClientProvider can disclose a client_secret, authorization code, PKCE code_verifier, or signed client assertion. MCP servers, stdio clients, and clients that attach their own tokens or headers are not affected. Interactive OAuthClientProvider use requires a person to start sign-in, while the unattended providers do not. For ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider, callers must configure issuer= after upgrading because omission still follows the MCP server's advertised authorization server, and the deprecated RFC7523OAuthClientProvider must be replaced because it has no issuer option. A stored client registration without an issuer remains unbound after upgrading, so stored OAuth client information must be cleared once to register again or a manually pre-registered record must be updated with its issuer. This issue is fixed in versions 1.30.0 and 2.2.0.6h
CVE-2026-1292977.5 ALT
—
———mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. Prior to 4.6.2, get_server_ipaddress() can select an attacker-controlled address from attacker-controlled Received headers. The minimum mechanism needed to distinguish this spoofing issue, derived from the advisory's remediation analysis and verified fix evidence, is appearance-based candidate selection that can treat bracketed IPv4 or IPv6 addresses or HELO markers in sender-written text as MTA-recorded addresses and can continue past a trusted hop that names no address. Applications that rely on the returned value can attribute a message to an attacker-selected sender IP address. This issue is fixed in version 4.6.2.10h
CVE-2026-1292589.1 CRÍ
17.3%
——5A vulnerability was identified in Tenda AC18 15.03.05.05_multi/15.03.05.19 Build 6318. Affected by this vulnerability is an unknown functionality of the file /cgi-bin/upgrade of the component Firmware Upgrade Handler. Such manipulation of the argument upgradeFile leads to insufficient verification of data authenticity. The attack may be launched remotely. The exploit is publicly available and might be used.12h
CVE-2026-68551—
20.5%
——6Budget Board is an app for tracking monthly spending and working towards financial goals. Prior to version 3.6.2, Budget Board's OIDC login flow finds and signs into an existing local account purely by matching the email address asserted in the identity provider's token - it never checks the standard email_verified claim. If the configured OIDC provider ever allows a user to register or display an email address without proving they own it , an attacker can register there using a victim's email and get signed into the victim's existing Budget Board account - including all their linked bank data. This issue has been patched in version 3.6.2.3d
CVE-2026-754896.8 MED
7.1%
——2Cudy TR3000 before 2.5.42 contains an insufficient verification of data authenticity vulnerability in the mt_wifi Smart Mesh Technology (SMT) onboarding, which protects messages only with an AES-CBC key derived from public values and a CRC32 check. Adjacent unauthenticated attackers can forge SMT messages in Probe Request vendor IEs carrying an attacker-chosen SSID and pre-shared key, forcing unpaired devices to join attacker-controlled access points.8h
CVE-2026-1164304.3 MED
1.4%
——0Dell PowerScale InsightIQ, Version 6.4.0, contain an Insufficient Verification of Data Authenticity vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Information tampering.4d