Vulnerabilities

With the aim of informing, warning and helping professionals with the latest security vulnerabilities in technology systems, we have made a database available for users interested in this information, which is in Spanish and includes all of the latest documented and recognised vulnerabilities.

This repository, with over 75,000 registers, is based on the information from the NVD (National Vulnerability Database) – by virtue of a partnership agreement – through which INCIBE translates the included information into Spanish.

On occasions this list will show vulnerabilities that have still not been translated, as they are added while the INCIBE team is still carrying out the translation process. The CVE  (Common Vulnerabilities and Exposures) Standard for Information Security Vulnerability Names is used with the aim to support the exchange of information between different tools and databases.

All vulnerabilities collected are linked to different information sources, as well as available patches or solutions provided by manufacturers and developers. It is possible to carry out advanced searches, as there is the option to select different criteria to narrow down the results, some examples being vulnerability types, manufacturers and impact levels, among others.

Through RSS feeds or Newsletters we can be informed daily about the latest vulnerabilities added to the repository. Below there is a list, updated daily, where you can discover the latest vulnerabilities.

CVE-2026-70461

Publication date:
13/08/2026
rsync 3.2.5 before 3.5.0 contains a heap out-of-bounds write vulnerability that allows remote unauthenticated attackers to write one attacker-controlled byte past the end of a heap allocation by supplying a crafted files-from entry. Attackers can trigger the vulnerability against a read-only rsync daemon module by providing a files-from entry containing both an interior and trailing backslash, causing the add_implied_include() function to under-count the trailing backslash when sizing the destination buffer.
Severity CVSS v4.0: HIGH
Last modification:
31/08/2026

CVE-2026-70456

Publication date:
13/08/2026
rsync 3.0.1 before 3.5.0 contains an out-of-bounds write vulnerability in the read_args() function that allows a malicious sender to corrupt adjacent heap memory by sending a crafted argument list. When the argument count causes the argv allocation to be exactly full, the trailing NULL terminator is written one slot beyond the allocation boundary, corrupting adjacent heap memory.
Severity CVSS v4.0: HIGH
Last modification:
14/08/2026

CVE-2026-70460

Publication date:
13/08/2026
rsync 2.3.3 before 3.5.0 contains a path traversal vulnerability that allows a malicious sender to escape the module root by exploiting symlinks within the module file tree when using --partial-dir or --backup-dir options. Attackers with write access to place a symlink under the module root, or who can exploit a pre-existing trusted symlink, can direct file writes to locations outside the intended module root, achieving arbitrary file write relative to the module root parent.
Severity CVSS v4.0: CRITICAL
Last modification:
14/08/2026

CVE-2026-70454

Publication date:
13/08/2026
rsync 3.2.0 through 3.2.3 (openssl mode) and rsync-ssl through 3.4.4 (stunnel mode) contain a TLS certificate validation vulnerability that allows on-path attackers to intercept encrypted sessions by presenting self-signed or otherwise invalid certificates. Attackers can exploit the failure to validate server TLS certificates against a trusted CA or verify certificate hostname matching to decrypt or tamper with rsync session content without detection by the client.
Severity CVSS v4.0: HIGH
Last modification:
13/08/2026

CVE-2026-70458

Publication date:
13/08/2026
rsync 3.0.0 before 3.5.0 contains an out-of-bounds write vulnerability that allows attackers to corrupt memory by triggering HLINK_BUMP processing on file entries with the FLAG_HLINKED flag set while the hard-link preservation option is inactive. Attackers can exploit the missing F_SUM field in the file_struct layout to access memory past the end of the allocated structure, corrupting adjacent heap or stack data.
Severity CVSS v4.0: HIGH
Last modification:
13/08/2026

CVE-2026-70455

Publication date:
13/08/2026
rsync 3.4.2 before 3.5.0 contains a denial of service vulnerability that allows a remote sender to exhaust system resources by specifying the --zt short alias for --compress-threads, which bypasses the refuse options directive's string matching on long option names. Attackers can specify --zt=N with a large value to spawn an unbounded number of Zstandard worker threads on the receiver, exhausting available thread and memory resources.
Severity CVSS v4.0: HIGH
Last modification:
31/08/2026

CVE-2026-70459

Publication date:
13/08/2026
rsync 3.0.0 before 3.5.0 contains a null pointer dereference vulnerability in the daemon child process that allows remote attackers to crash the daemon by sending a file list whose first entry is a dot entry not typed as a directory. The daemon dereferences the first file list entry as a directory structure pointer without verifying the entry type, resulting in an invalid or uninitialized pointer dereference that terminates the client connection.
Severity CVSS v4.0: MEDIUM
Last modification:
31/08/2026

CVE-2026-70457

Publication date:
13/08/2026
rsync 3.2.3 before 3.5.0 contains an out-of-bounds write in parse_size_arg() where the return value of snprintf() is used directly as an index into a .bss-segment array without bounds checking. When snprintf truncates the formatted size string, the return value equals the number of characters that would have been written including the truncated portion, and this value may exceed the array length. The subsequent indexed write targets memory outside the intended array bounds, corrupting .bss memory.
Severity CVSS v4.0: HIGH
Last modification:
31/08/2026

CVE-2026-70452

Publication date:
13/08/2026
rsync 3.1.0 before 3.5.0 contains an access control bypass vulnerability that allows remote attackers to circumvent hosts deny rules by inducing DNS resolution failures during hostname-based access control evaluation. When a DNS lookup for a hostname-based deny rule fails, the daemon skips the rule rather than defaulting to a deny decision, enabling attackers who can trigger DNS failures to bypass module-level IP access controls and gain unauthorized access to restricted module file trees.
Severity CVSS v4.0: CRITICAL
Last modification:
14/08/2026

CVE-2026-70453

Publication date:
13/08/2026
rsync before 3.5.0 contains an algorithmic complexity vulnerability in the hash_search() function that allows a remote attacker to cause a denial of service by delivering a carefully constructed file list. A sender can exploit the quadratic-time worst-case behavior in hash lookups to exhaust receiver CPU resources with a modest number of crafted entries, causing a sustained denial of service.
Severity CVSS v4.0: HIGH
Last modification:
13/08/2026

CVE-2026-6387

Publication date:
13/08/2026
A potential authentication bypass vulnerability was reported in Lenovo System Update that could allow a local authenticated user to execute arbitrary code with elevated privileges.
Severity CVSS v4.0: HIGH
Last modification:
24/08/2026

CVE-2026-68453

Publication date:
13/08/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> s390/zcrypt: Fix buffer over-read in cca_cipher2protkey<br /> <br /> Add validation of both the actual key buffer size and token length<br /> fields in all the cca_check_sec*token() functions. Additionally check<br /> in cca_gencipherkey() for possible underflow with returned key size.<br /> <br /> The CCA token structures contain user-controlled len fields that<br /> were used in operations without proper validation against both the<br /> actual buffer size and minimum token structure size. An attacker<br /> could set this field larger than the actual buffer size, leading to<br /> reading beyond buffer boundaries. This may result in a kernel crash or<br /> exposure of memory via sending this as part of a request down to the<br /> crypto card. Also an attacker could have used a very small len value<br /> and thus enforce a buffer under-run which may produce similar effects<br /> as a over-read.<br /> <br /> So now a key must<br /> - key buf length must be at least sizeof the token struct<br /> - the key len field inside the token must fit into the range of<br /> sizeof key token struct ... key buf length
Severity CVSS v4.0: Pending analysis
Last modification:
17/08/2026