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-2025-26691

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-26693

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-27131

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-27242

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through improper input.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-27247

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-27563

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through get permission.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-21082

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-23235

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause DOS through out-of-bounds read.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-24493

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause information leak through race condition.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-25217

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-20063

Publication date:
08/06/2025
in OpenHarmony v5.0.3 and prior versions allow a local attacker cause apps crash through type confusion.
Severity CVSS v4.0: Pending analysis
Last modification:
09/06/2025

CVE-2025-38004

Publication date:
08/06/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> can: bcm: add locking for bcm_op runtime updates<br /> <br /> The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via<br /> hrtimer. The content and also the length of the sequence can be changed<br /> resp reduced at runtime where the &amp;#39;currframe&amp;#39; counter is then set to zero.<br /> <br /> Although this appeared to be a safe operation the updates of &amp;#39;currframe&amp;#39;<br /> can be triggered from user space and hrtimer context in bcm_can_tx().<br /> Anderson Nascimento created a proof of concept that triggered a KASAN<br /> slab-out-of-bounds read access which can be prevented with a spin_lock_bh.<br /> <br /> At the rework of bcm_can_tx() the &amp;#39;count&amp;#39; variable has been moved into<br /> the protected section as this variable can be modified from both contexts<br /> too.
Severity CVSS v4.0: Pending analysis
Last modification:
17/12/2025