CVE-2026-82932
mH-DEVELOPER smart home module does not load any firewall rules at startup. This leaves all listening services, including SSH, HTTP, WebSock
CVSS
—
Sin CVSS
EPSS
0.2%
p7
KEV
—
Exploit Today
2
0-100
Publicado: 28 sept 2026 · Última mod.: 28 sept 2026 · CWE-923
0.2%EPSS · 30 días0.2%
2026-09-292026-10-25
mH-DEVELOPER smart home module does not load any firewall rules at startup. This leaves all listening services, including SSH, HTTP, WebSocket, and Node-RED, fully exposed on the LAN without access control. Any client on the same network can reach every service. This issue was fixed in version 3.0.30
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-1109095.0 MED2.9%
——1Wheels CLI through 4.1.0 does not verify that the local development server answering its HTTP requests belongs to the current project. A process listening on a port targeted by the CLI can receive the project's reload password and code submitted through wheels reload or wheels console; console also probes common ports when the project server is down. Other commands can perform unintended state-changing operations against a different local application's server and database. Exploitation requires a process listening on a targeted local port and the developer running an affected command. This is fixed in 4.1.1, including changes to the CLI and application template.6dCVE-2026-1020856.5 MED21.0%
——6An Improper Restriction of Communication Channel to Intended Endpoints vulnerability in Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a limited information disclosure and availability impact to the device.
Due to a wrong initialization, a process which should only be able to communicate internally within the device can be reached over the network via an open port. This leads to a device being inadvertently exposed and increased CPU cycles spent processing ingress packets.
This issue affects Junos OS Evolved:
* All versions before 23.2R2-S7.7-EVO;
* 23.4 versions before 23.4R2-S8.11-EVO;
* 24.2 versions before 24.2R2-S5.6-EVO;
* 24.4 versions before 24.4R2-S4-EVO;
* 25.2 version before 25.2R2-S1-EVO;
* 25.4 versions before 25.4R1-S1-EVO.
Please note that this issue is similar to but not identical CVE-2026-33803.10dCVE-2026-859258.2 ALT44.2%
——13Improper restriction of communication channel to intended endpoints in Azure Key Vault allows an authorized attacker to elevate privileges over a network.9dCVE-2026-702127.0 ALT19.6%
——6Improper restriction of communication channel to intended endpoints in Windows Security Center allows an authorized attacker to elevate privileges locally.9dCVE-2026-863459.0 CRÍ32.0%
——10A flaw was found in 389-ds-base. The server does not discard plaintext bytes already buffered from a client connection when negotiating StartTLS, allowing an on-path attacker to inject a crafted LDAP message that is processed after the TLS upgrade and whose response is delivered to the client in place of the client's own pending operation's response, due to messageID collision. This can cause a client application to treat a failed authentication (bind) attempt as successful.18dCVE-2026-921739.1 CRÍ21.1%
——6Prior to v74.0.0.878.1682 of Meta Horizon OS, MediaSyncJobReceiver could be induced to send a privileged PendingIntent including a com.oculus.vrshell CallerIdentity to an arbitrary application listening via NotificationListenerService. That would allow the application to impersonate the com.oculus.vrshell package, as well as packages signed with the same key, towards any endpoint within the OS that uses CallerIdentity authentication.24d