CVE-2026-2261
HighSummary
Z powodu błędu programistycznego, blocklistd ujawnia deskryptor gniazda dla każdego zgłoszenia o zdarzeniu negatywnym, co prowadzi do wyczerpania dostępnych deskryptorów. Po osiągnięciu krytycznej liczby wycieków, blocklistd przestaje działać poprawnie, co uniemożliwia blokowanie nowych adresów oraz odblokowywanie wygasłych wpisów.
Risk Assessment
Atakujący może wykorzystać tę podatność, generując dużą liczbę zdarzeń negatywnych z fałszywych adresów IP, co skutkuje dezaktywacją blocklistd przed przeprowadzeniem ataku. Regularne występowanie zdarzeń negatywnych w normalnej pracy również prowadzi do wyczerpania deskryptorów plików.
Recommendation
Zaleca się monitorowanie i ograniczenie liczby zgłoszeń o zdarzeniach negatywnych oraz wprowadzenie mechanizmów ochrony przed nadmiernym obciążeniem blocklistd. Należy również rozważyć aktualizację oprogramowania w celu naprawy błędu programistycznego.
Related vulnerabilities
- CVE-2026-81855Critical
A hardcoded cryptographic client authentication key vulnerability exists in the robot testing framework component of Wärtsilä FOS-Onboard. The key is embedded in the software and cannot be changed by administrators.
- CVE-2026-78225Critical
A hardcoded cryptographic server key vulnerability exists in the deployer-ng Update Controller component of Wärtsilä FOS-Onboard. The key is embedded in the software and cannot be changed by administrators.
- CVE-2026-73807Critical
The mySCADA myPRO Manager command API does not properly enforce authentication for privileged functions. An unauthenticated attacker with network access to the affected API could exploit this vulnerability to access privileged management functions.
- CVE-2026-73437Critical
On affected platforms running Arista EOS with Dynamic Host Configuration Protocol (DHCP) relay configured, an unauthenticated attacker with network access could send a crafted DHCP reply packet from an IP address that is not configured as a helper address, and the relay agent would forward it to clients without validating the source.
- CVE-2026-61560Critical
`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Prior to version 2.1.27, the SSE transport mode (`SSE=true`) exposes all MCP tools without any authentication. The `upload_markdown` tool reads arbitrary files from the server's local filesystem via an unsanitized `file_path` parameter and uploads them to a GitLab project.
- CVE-2026-91939Critical
Cotonti 1.0.0 Comments plugin passes the ci GET parameter to unserialize() without allowed_classes restriction, allowing unauthenticated attackers to instantiate arbitrary PHP classes with attacker-controlled properties. Attackers can exploit PHP object injection through crafted serialized payloads to trigger gadget chains and achieve database manipulation or code execution.
- CVE-2026-68491Critical
An insufficient check allowed for the overwrite of arbitrary files via a symlink. Technical details were not provided in the description.
- CVE-2026-66890Critical
The affected products use hard-coded credentials, which could allow remote access to files with root privileges where FTP is reachable. Technical details were not provided in the description.
- CVE-2026-66887Critical
The affected products are missing authorization on state-changing CGIs and session checks are not performed. Technical details were not provided in the description.
- CVE-2026-61568Critical
`@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. Versions prior to 2.1.30 expose the Streamable HTTP MCP endpoint without an effective Host or Origin allowlist. A malicious web page can use DNS rebinding to route browser requests to a victim's local MCP listener while preserving an attacker-controlled `Host` and `Origin`.
Original NVD description (English source)
Due to a programming error, blocklistd leaks a socket descriptor for each adverse event report it receives. Once a certain number of leaked sockets is reached, blocklistd becomes unable to run the helper script: a child process is forked, but this child dereferences a null pointer and crashes before it is able to exec the helper. At this point, blocklistd still records adverse events but is unable to block new addresses or unblock addresses whose database entries have expired. Once a second, much higher number of leaked sockets is reached, blocklistd becomes unable to receive new adverse event reports. An attacker may take advantage of this by triggering a large number of adverse events from sacrificial IP addresses to effectively disable blocklistd before launching an attack. Even in the absence of attacks or probes by would-be attackers, adverse events will occur regularly in the course of normal operations, and blocklistd will gradually run out file descriptors and become ineff