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-62144

Publication date:
22/07/2026
An authentication bypass vulnerability in Check Point Security Management and Multi-Domain Security Management allows an unauthenticated remote attacker to execute administrative commands on the Management Server. Successful exploitation may also allow command execution on managed Security Gateways. Exploitation requires network access to the Management Server without firewall protection or a configuration that does not restrict Trusted Clients.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-62145

Publication date:
22/07/2026
A vulnerability in Check Point Gaia Portal allows an authenticated attacker with read-only Gaia Portal privileges to execute commands with root privileges.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-56444

Publication date:
22/07/2026
In NLnet Labs Unbound 1.20.0 up to and including 1.25.1, when Unbound is configured with 'serve-expired: yes' and 'serve-expired-client-timeout > discard-timeout > 0' (contrary to the suggested values), the discard-timeout branch during the serve expired logic drops an aged client reply without performing the correct accounting for the number of reply addresses for the query. Other identical branches outside of serve expired perform the correct decrement. Since the counter is never decremented in such scenario, it can reach the maximum limit and new clients for duplicate in-flight queries are silently dropped resulting in degradation of resolution service. A malicious actor can exploit the vulnerability by querying the resolver for a client-controlled slow-on-demand authoritative zone that can drive the counter past the threshold. Shipped defaults for 'serve-expired-client-timeout: 1800' and 'discard-timeout: 1900' make the branch unreachable.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-56416

Publication date:
22/07/2026
In NLnet Labs Unbound up to and including version 1.25.1, when the validator builds the canonical RDATA form for an RRSIG-covered PX/RP/MINFO/SOA RRset, it computes the address of the second embedded domain name as 'datstart + dname_valid(datstart, ...)' and passes it straight to 'query_dname_tolower()' without checking that a second name is actually present in the RDATA. The wire-format parser accepts multi-dname RRs whose RDATA ends after the first name, so an attacker who runs a DNSSEC-signed authoritative server can deliver a record with an absent second domain name (e.g. SOA record) and cause 'query_dname_tolower()' to walk label-by-label through stale bytes in the per-worker 'env->scratch_buffer', past the end of that heap allocation if 'msg-buffer-size' has been lowered from the default. This leads to heap buffer overflow and on a release build the outcome relies heavily on the contents of the buffer tail and the adjacent heap chunk.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-53910

Publication date:
22/07/2026
diff3 tool from GNU diffutils is vulnerable to a heap‑based buffer overflow due to multiple signed integer overflows in line‑mapping calculations. Incorrect arithmetic in mapping line ranges can result in corrupted values being used for memory allocation and loop bounds.<br /> When processing crafted diff output, these overflows may cause the application to allocate insufficient memory and subsequently perform out‑of‑bounds writes during internal processing. <br /> An attacker who can control the output of the diff program used by diff3 (e.g. via --diff-program pointing to a malicious script) can trigger out-of-bounds writes, resulting in a crash and potentially remote code execution depending on the environment.<br /> <br /> <br /> This issue has been fixed in commit 9ff04d5b84743e331e80b589335a52c5480d1815
Severity CVSS v4.0: LOW
Last modification:
22/07/2026

CVE-2026-54478

Publication date:
22/07/2026
In NLnet Labs Unbound 1.18.0 up to and including 1.25.1, when Unbound listens on a &amp;#39;proxy-protocol-port&amp;#39; interface with &amp;#39;answer-cookie: yes&amp;#39;, the RFC 9018 server-cookie SipHash is computed over the proxy&amp;#39;s wire address instead of the PROXYv2-declared client. One server cookie obtained through a given proxy node therefore validates for every PROXYv2-declared source behind that node. On a UDP+proxy-protocol front, an off-path attacker can harvest one cookie with a single legitimate query, then replay it under any spoofed source and pass DNS Cookie checks that were deployed to defeat this in the first place.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-55708

Publication date:
22/07/2026
In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, the &amp;#39;view_local_data&amp;#39; and &amp;#39;view_local_datas&amp;#39; commands of &amp;#39;unbound-control&amp;#39; create a bare local zones tree for an already configured named view when the view is configured with no local data to begin with. However, the creation through the control interface omits adding the default-protected zones (e.g., RFC 1918 reverse, AS112 zones, .onion, .localhost). Once the local zone tree exists without the defaults, every query for a default-protected name from a client mapped to that view escapes to the public DNS via the iterator instead of being answered locally, bypassing local policy expectations.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-55717

Publication date:
22/07/2026
In NLnet Labs Unbound 1.10.0 up to and including 1.25.1, when &amp;#39;serve-expired: yes&amp;#39; is set together with a &amp;#39;response-ip: redirect&amp;#39; /&amp;#39;response-ip-data: CNAME &amp;#39; rule (or the RPZ &amp;#39;rpz-cname-override&amp;#39; equivalent), a remote client who controls any delegated domain can crash the daemon. The serve-expired-client-timeout callback runs a two-pass loop to chase the respip-generated CNAME alias; on the second pass it resets &amp;#39;alias_rrset&amp;#39; but not &amp;#39;partial_rep&amp;#39;. Later, this inconsistency leads to a NULL pointer dereference and an eventual crash. A malicious actor can exploit the vulnerability by controlling any zone that replies with an A/AAAA record that falls inside the configured response-ip/rpz subnet. By delaying the answer when the previous record has expired, the vulnerable path of &amp;#39;serve-expired-client-timeout&amp;#39; is taken leading to denial of service via the server crash.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-55973

Publication date:
22/07/2026
In NLnet Labs Unbound 1.23.0 up to and including 1.25.1, when &amp;#39;dns-error-reporting: yes&amp;#39; is set, the EDNS Report-Channel option (code 18) from the last upstream response is read and uses the option&amp;#39;s length as the length of the agent domain. When a domain name check is performed on the agent domain, the returned lenght is not used and if the agent domain is followed by garbage, those bytes are moved onto the tail of the synthetic &amp;#39;_er.&amp;#39; report query name. That query name is later used in the iterator via a subquery to send out the DNS Error Report and when Unbound tries to walk that query name during &amp;#39;find_closest_of_type()&amp;#39;, it strips labels using the query name length rather than stopping at the embedded root, walks one byte past it, and feeds the first garbage byte to &amp;#39;dname_query_hash()&amp;#39; as a label length writing over the stack variable &amp;#39;labuf&amp;#39;. One ordinary upstream response from a delegated zone the attacker controls is sufficient to terminate the daemon.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-55990

Publication date:
22/07/2026
In NLnet Labs Unbound 1.7.0 up to and including 1.25.1, when the &amp;#39;dnscrypt:&amp;#39; clause lists more &amp;#39;dnscrypt-provider-cert:&amp;#39; files than there are matching &amp;#39;dnscrypt-secret-key:&amp;#39; files, Unbound fills only the matched prefix and leaves the tail slots at the &amp;#39;0xdb&amp;#39; fill that libsodium&amp;#39;s allocator writes into every allocation. Unbound would then iterate over the number of cert files, not the actual slots, so it walks into a slot with garbage data filled with &amp;#39;0xdb&amp;#39; bytes. Any unauthenticated client that sends one UDP datagram of ≥ 68 bytes whose first 8 bytes are &amp;#39;0xdb&amp;#39; to &amp;#39;dnscrypt-port&amp;#39; will use that garbage entry which leads to a garbage dereference killing the server. This is a silent faulty configuration that goes unnoticed until triggered with the right client query. Unbound needs to be compiled with DNSCrypt support (&amp;#39;--enable-dnscrypt&amp;#39;).
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-55991

Publication date:
22/07/2026
In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a remote unauthenticated client can trigger a libngtcp2 assertion (if compiled with assertions on) and terminate the entire Unbound process using a single DNS-over-QUIC (DoQ) connection and one normal DNS query. This is caused by an erroneous error value passed to libngtcp2. When &amp;#39;ngtcp2_conn_writev_stream()&amp;#39; returns &amp;#39;NGTCP2_ERR_STREAM_DATA_BLOCKED&amp;#39;, Unbound continues to call &amp;#39;ngtcp2_ccerr_set_application_error()&amp;#39; with a &amp;#39;-1&amp;#39; error value. The &amp;#39;int&amp;#39; literal &amp;#39;-1&amp;#39; is implicitly converted to the function&amp;#39;s &amp;#39;uint64_t error_code&amp;#39; parameter as &amp;#39;0xFFFFFFFFFFFFFFFF&amp;#39;. The follow-on &amp;#39;ngtcp2_conn_write_connection_close()&amp;#39; serialises that value as a QUIC variable-length integer; because &amp;#39;2^64-1&amp;#39; exceeds the 62-bit varint ceiling, &amp;#39;ngtcp2_put_uvarintlen()&amp;#39; fails &amp;#39;assert(n
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026

CVE-2026-50046

Publication date:
22/07/2026
In NLnet Labs Unbound 1.15.0 up to and including 1.25.1, the TLS server name used for DNS-over-TLS (DoT) forwarded queries is tied to a struct&amp;#39;s (&amp;#39;serviced_query&amp;#39;) lifetime but also referenced by another struct (&amp;#39;waiting_tcp&amp;#39;). When the owning struct is jostled out of the mesh while the DoT TCP stream is still handshaking it frees the storage behind the referenced string and if the TLS stream then errors out, it dereferences the freed pointer. The dereference is read-only and the practical impact is a daemon crash resulting in denial of service. A malicious actor that knows a DoT forwarding/stub Unbound&amp;#39;s configuration could exploit the vulnerability by quering records in the appropriate zone while keeping Unbound uder pressure so that the jostle logic kicks in. If answers for the vulnerable zone are slow, the likelihood of jostling such queries is higher, although the timing of the jostle needs to be precise. Requirements for a vulnerable Unbound is the existence of a stub/forward zone configured for DoT together with a configured &amp;#39;#authname&amp;#39; suffix on the server identification. The connectivity to the server needs to exhibit a transient failure at the correct time in order to kick off the vulnerable error path.
Severity CVSS v4.0: Pending analysis
Last modification:
24/07/2026