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

Publication date:
28/07/2026
Accesses to the CMOS memory contents are done using an indirect IO port<br /> pair. Therefore Xen needs to cache the guest chosen index, and one of<br /> the usages of the index didn&amp;#39;t take the necessary locking to avoid<br /> concurrent changes. As a result, a guest could change the index after<br /> it being checked, causing a subsequent out-of-bound read access to the<br /> contents of an array.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-62423

Publication date:
28/07/2026
[This CNA information record relates to multiple CVEs; the<br /> text explains which aspects/vulnerabilities correspond to which CVE.]<br /> <br /> The directory and Rock Ridge / SUSP walk in libfsimage&amp;#39;s iso9660 driver<br /> derives several lengths directly from attacker-controlled on-disk fields<br /> without validating them:<br /> <br /> * The directory loop itself assumes a good record length. This is<br /> CVE-2026-42494.<br /> <br /> * The calculation of the System Use area may underflow. This is<br /> CVE-2026-42495.<br /> <br /> * The Rock Ridge extension loop assumes a good (inner) record length.<br /> This is CVE-2026-62423.<br /> <br /> * The Rock Ridge NM record processing assumes a good entry length.<br /> This is CVE-2026-62424.<br /> <br /> * The Rock Ridge CE record processing assumes a good size and offset.<br /> This is CVE-2026-62425.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-62424

Publication date:
28/07/2026
[This CNA information record relates to multiple CVEs; the<br /> text explains which aspects/vulnerabilities correspond to which CVE.]<br /> <br /> The directory and Rock Ridge / SUSP walk in libfsimage&amp;#39;s iso9660 driver<br /> derives several lengths directly from attacker-controlled on-disk fields<br /> without validating them:<br /> <br /> * The directory loop itself assumes a good record length. This is<br /> CVE-2026-42494.<br /> <br /> * The calculation of the System Use area may underflow. This is<br /> CVE-2026-42495.<br /> <br /> * The Rock Ridge extension loop assumes a good (inner) record length.<br /> This is CVE-2026-62423.<br /> <br /> * The Rock Ridge NM record processing assumes a good entry length.<br /> This is CVE-2026-62424.<br /> <br /> * The Rock Ridge CE record processing assumes a good size and offset.<br /> This is CVE-2026-62425.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-62425

Publication date:
28/07/2026
[This CNA information record relates to multiple CVEs; the<br /> text explains which aspects/vulnerabilities correspond to which CVE.]<br /> <br /> The directory and Rock Ridge / SUSP walk in libfsimage&amp;#39;s iso9660 driver<br /> derives several lengths directly from attacker-controlled on-disk fields<br /> without validating them:<br /> <br /> * The directory loop itself assumes a good record length. This is<br /> CVE-2026-42494.<br /> <br /> * The calculation of the System Use area may underflow. This is<br /> CVE-2026-42495.<br /> <br /> * The Rock Ridge extension loop assumes a good (inner) record length.<br /> This is CVE-2026-62423.<br /> <br /> * The Rock Ridge NM record processing assumes a good entry length.<br /> This is CVE-2026-62424.<br /> <br /> * The Rock Ridge CE record processing assumes a good size and offset.<br /> This is CVE-2026-62425.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-62426

Publication date:
28/07/2026
[This CNA information record relates to multiple CVEs; the<br /> text explains which aspects/vulnerabilities correspond to which CVE.]<br /> <br /> To manage the system, sysctl and platform operations are used by the<br /> control domain or a possible Xenstore domain. Some of these operations<br /> may not be executed in parallel, so a system-wide lock each is used.<br /> The way those locks are acquired is, however, not providing any fairness.<br /> Furthermore, with XSM/Flask in use, the lock acquire will, for some<br /> operations, occur ahead of any permission checking.<br /> <br /> The sysctl issue is CVE-2026-62426.<br /> <br /> The platform-op issue is CVE-2026-62427.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-62427

Publication date:
28/07/2026
[This CNA information record relates to multiple CVEs; the<br /> text explains which aspects/vulnerabilities correspond to which CVE.]<br /> <br /> To manage the system, sysctl and platform operations are used by the<br /> control domain or a possible Xenstore domain. Some of these operations<br /> may not be executed in parallel, so a system-wide lock each is used.<br /> The way those locks are acquired is, however, not providing any fairness.<br /> Furthermore, with XSM/Flask in use, the lock acquire will, for some<br /> operations, occur ahead of any permission checking.<br /> <br /> The sysctl issue is CVE-2026-62426.<br /> <br /> The platform-op issue is CVE-2026-62427.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-49332

Publication date:
28/07/2026
A flaw was found in openshift/oauth-proxy. The proxy sets authenticated identity headers using only dash-variant keys (X-Forwarded-User) but does not strip underscore-variant keys (X_Forwarded_User) from incoming requests. WSGI and PHP frameworks normalize both variants to the same variable, allowing an authenticated low-privilege user to smuggle a forged identity that may override the legitimate authenticated identity in the upstream application.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-42492

Publication date:
28/07/2026
Xenstore, to have an up-to-date picture of the entire system, wants to<br /> know of domains appearing and disappearing. To make this more robust, a<br /> new XEN_DOMCTL_get_domain_state was introduced. The management of the<br /> bitmap underlying that operation is tied into the binding of the<br /> VIRQ_DOM_EXC virtual IRQ. Unfortunately an error path there would tear<br /> down the bitmap even in cases when it wasn&amp;#39;t set up. Unprivileged domains<br /> can trigger that error path.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-42493

Publication date:
28/07/2026
Addressing certain issues, in particular related to operations which may<br /> take excessively long and therefore would need preemption, has turned out<br /> overly costly. Since alternatives (HVM/PVH: HAP, PV: shim) are commonly<br /> available, the decision was to deprecate the functionality, while still<br /> retaining it for people to use at their own (security) risk. Memory-wise<br /> small enough guests may still be okay to run.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-42494

Publication date:
28/07/2026
[This CNA information record relates to multiple CVEs; the<br /> text explains which aspects/vulnerabilities correspond to which CVE.]<br /> <br /> The directory and Rock Ridge / SUSP walk in libfsimage&amp;#39;s iso9660 driver<br /> derives several lengths directly from attacker-controlled on-disk fields<br /> without validating them:<br /> <br /> * The directory loop itself assumes a good record length. This is<br /> CVE-2026-42494.<br /> <br /> * The calculation of the System Use area may underflow. This is<br /> CVE-2026-42495.<br /> <br /> * The Rock Ridge extension loop assumes a good (inner) record length.<br /> This is CVE-2026-62423.<br /> <br /> * The Rock Ridge NM record processing assumes a good entry length.<br /> This is CVE-2026-62424.<br /> <br /> * The Rock Ridge CE record processing assumes a good size and offset.<br /> This is CVE-2026-62425.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-42495

Publication date:
28/07/2026
[This CNA information record relates to multiple CVEs; the<br /> text explains which aspects/vulnerabilities correspond to which CVE.]<br /> <br /> The directory and Rock Ridge / SUSP walk in libfsimage&amp;#39;s iso9660 driver<br /> derives several lengths directly from attacker-controlled on-disk fields<br /> without validating them:<br /> <br /> * The directory loop itself assumes a good record length. This is<br /> CVE-2026-42494.<br /> <br /> * The calculation of the System Use area may underflow. This is<br /> CVE-2026-42495.<br /> <br /> * The Rock Ridge extension loop assumes a good (inner) record length.<br /> This is CVE-2026-62423.<br /> <br /> * The Rock Ridge NM record processing assumes a good entry length.<br /> This is CVE-2026-62424.<br /> <br /> * The Rock Ridge CE record processing assumes a good size and offset.<br /> This is CVE-2026-62425.
Severity CVSS v4.0: Pending analysis
Last modification:
28/07/2026

CVE-2026-41874

Publication date:
28/07/2026
Quick.Cart stores hard-coded, plaintext admin credentials in a configuration file. This flaw allows attackers with access to the server file system to retrieve authentication details, potentially leading to privilege escalation.<br /> <br /> <br /> The vendor assessed the likelihood of exploitation as very low and determined that a fix is not necessary.<br /> <br /> <br /> <br /> Only version 6.7 was tested but all versions should be considered as vulnerable.
Severity CVSS v4.0: MEDIUM
Last modification:
30/07/2026