https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-08T04:39:19.615480+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-245711 EUVD-2026-245711 2026-10-08T04:39:19.660350+00:00 EUVD-2026-245711 https://cve.radiocsirt.org/vuln/fkie_cve-2025-52570 fkie_cve-2025-52570 2026-10-08T04:39:19.660387+00:00

Letmein is an authenticating port knocker. Prior to version 10.2.1, The connection limiter is implemented incorrectly. It allows an arbitrary amount of simultaneously incoming connections (TCP, UDP and Unix socket) for the services letmeind and letmeinfwd. Therefore, the command line option num-connections is not effective and does not limit the number of simultaneously incoming connections. This issue has been patched in version 10.2.1.

 https://cve.radiocsirt.org/vuln/ghsa-jpv7-p47h-f43j GHSA-jpv7-p47h-f43j — letmein connection limiter allows an arbitrary amount of simultaneous connections 2026-10-08T04:39:19.660421+00:00

Affected: crates.io: letmeind, crates.io: letmeinfwd

### Impact

The connection limiter is implemented incorrectly. It allows an arbitrary amount of simultaneously incoming connections (TCP, UDP and Unix socket) for the services `letmeind` and `letmeinfwd`. Therefore, the command line option `num-connections` is not effective and does not limit the number of simultaneously incoming connections.

`letmeind` is the public network facing daemon (TCP/UDP).

`letmeinfwd` is the internal firewall daemon that only listens on local Unix socket.

Possible Denial Of Service by resource exhaustion.

### Affected versions All versions `<= 10.2.0` are affected.

### Patches All users shall upgrade to version `10.2.1`.

### Workarounds

Untested possible workarounds: - It might be possible to limit the number of active connections to the `letmeind` port (default 5800) via firewall. - The resource consumption of the service might be restricted with a service manager such as systemd.

### Severity:

If a (D)DoS is run against the service, *something* is going to be affected. The connection limiter assures that the effect on the system itself is limited at the expense of the effect on the letmein services itself. So even with the connection limiter active, a (D)DoS can lead to a less responsive or unresponsive letmein service.