Instituto Nacional de ciberseguridad. Sección Incibe
Instituto Nacional de Ciberseguridad. Sección INCIBE-CERT

017 - Ir a la línea de ayuda en Ciberseguridad    Ir a Agenda     Ir a Sala de prensa     Ir a suscripción de boletines

Ir al buscador

Vulnerabilidades

Con el objetivo de informar, advertir y ayudar a los profesionales sobre las últimas vulnerabilidades de seguridad en sistemas tecnológicos, ponemos a disposición de los usuarios interesados en esta información una base de datos con información en castellano sobre cada una de las últimas vulnerabilidades documentadas y conocidas.

Este repositorio con más de 75.000 registros esta basado en la información de NVD (National Vulnerability Database) – en función de un acuerdo de colaboración – por el cual desde INCIBE realizamos la traducción al castellano de la información incluida. En ocasiones este listado mostrará vulnerabilidades que aún no han sido traducidas debido a que se recogen en el transcurso del tiempo en el que el equipo de INCIBE realiza el proceso de traducción.

Se emplea el estándar de nomenclatura de vulnerabilidades CVE (Common Vulnerabilities and Exposures), con el fin de facilitar el intercambio de información entre diferentes bases de datos y herramientas. Cada una de las vulnerabilidades recogidas enlaza a diversas fuentes de información así como a parches disponibles o soluciones aportadas por los fabricantes y desarrolladores. Es posible realizar búsquedas avanzadas teniendo la opción de seleccionar diferentes criterios como el tipo de vulnerabilidad, fabricante, tipo de impacto entre otros, con el fin de acortar los resultados.

Mediante suscripción RSS o Boletines podemos estar informados diariamente de las últimas vulnerabilidades incorporadas al repositorio.

CVE-2026-2395
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** Improper neutralization of special elements used in an SQL command (&amp;#39;SQL injection&amp;#39;) vulnerability in Xpoda Türkiye Informatics Technology Inc. No Code Platform allows SQL Injection.<br /> <br /> This issue affects No Code Platform: from 4.3.1.0 through 20260722. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
Gravedad CVSS v3.1: CRÍTICA
Última modificación:
22/07/2026

CVE-2026-13204
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof.<br /> This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: ALTA
Última modificación:
22/07/2026

CVE-2026-13321
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer&amp;#39;s zone.<br /> This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: ALTA
Última modificación:
22/07/2026

CVE-2026-14985
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** The Analog Way Picturall Quad Compact Mark II version 3.5.8, contains a local privilege escalation vulnerability in the core firmware. This is due to improper privilege delegation and insufficient input validation in a maintenance script.
Gravedad: Pendiente de análisis
Última modificación:
22/07/2026

CVE-2026-10723
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses.<br /> This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: MEDIA
Última modificación:
22/07/2026

CVE-2026-10822
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit.<br /> <br /> BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorithm (253), and in the algorithm identifier, improperly give a length longer than the actual identifier data. The invalid identifier will be stored. If BIND later needs to render that record to text, it will use the invalid length during processing, leading to a consistency check failing.<br /> This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: MEDIA
Última modificación:
22/07/2026

CVE-2026-11331
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It also may lead to an unexpected exit of the BIND 9 software.<br /> This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: ALTA
Última modificación:
22/07/2026

CVE-2026-11605
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** The issue is a resource exhaustion vulnerability associated with DNSSEC validation. BIND always validates all RRSIG records in an answer, even if they are not strictly needed. A query to an authoritative server/zone which returns many valid but superfluous RRSIG records causes the validator to waste disproportionate CPU time.<br /> This issue affects BIND 9 versions 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: ALTA
Última modificación:
22/07/2026

CVE-2026-11622
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage can be orders of magnitude beyond the limit configured in the `max-cache-size` parameter.<br /> This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: ALTA
Última modificación:
22/07/2026

CVE-2026-11721
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** It is possible for an attacker&amp;#39;s zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes `named` to produce a wildcard name for a zone that is shorter than the attacker&amp;#39;s zone, which can result in cache poisoning. For this attack to have any effect, the resolver under attack must have set `synth-from-dnssec yes;` (which is the default).<br /> This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: ALTA
Última modificación:
22/07/2026

CVE-2026-12617
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative server responds positively to the A query but delays the DNAME response and later responds negatively, `named` may quit unexpectedly. Or, if a client queries for a CNAME and A record for the same name to the resolver, and the authoritative server responds positively to the A query but delays the CNAME response and later responds with a self-referential CNAME, the same failure may occur.<br /> This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.
Gravedad CVSS v3.1: ALTA
Última modificación:
22/07/2026

CVE-2026-56444
Fecha de publicación:
22/07/2026
Idioma:
Inglés
*** Pendiente de traducción *** In NLnet Labs Unbound 1.20.0 up to and including 1.25.1, when Unbound is configured with &amp;#39;serve-expired: yes&amp;#39; and &amp;#39;serve-expired-client-timeout &gt; discard-timeout &gt; 0&amp;#39; (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 &amp;#39;serve-expired-client-timeout: 1800&amp;#39; and &amp;#39;discard-timeout: 1900&amp;#39; make the branch unreachable.
Gravedad CVSS v3.1: MEDIA
Última modificación:
22/07/2026
Suscribirse a Vulnerabilidades