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

Go to Calendar     Go to Press Room     Go to Newsletters subscription

Search

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-2024-35322
Publication date:
24/12/2025
MyNET up to v26.08 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the ficheiro parameter.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-2155
Publication date:
24/12/2025
Unrestricted Upload of File with Dangerous Type vulnerability in Echo Call Center Services Trade and Industry Inc. Specto CM allows Remote Code Inclusion.This issue affects Specto CM: before 17032025.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-60935
Publication date:
24/12/2025
An open redirect vulnerability in the login endpoint of Blitz Panel v1.17.0 allows attackers to redirect users to malicious domains via a crafted URL. This issue affects the next_url parameter in the login endpoint and could lead to phishing or token theft after successful authentication.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-2154
Publication date:
24/12/2025
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Echo Call Center Services Trade and Industry Inc. Specto CM allows Stored XSS.This issue affects Specto CM: before 17032025.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-5448
Publication date:
24/12/2025
Rejected reason: This CVE id was assigned but later discarded.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-68741
Publication date:
24/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: qla2xxx: Fix improper freeing of purex item<br /> <br /> In qla2xxx_process_purls_iocb(), an item is allocated via<br /> qla27xx_copy_multiple_pkt(), which internally calls<br /> qla24xx_alloc_purex_item().<br /> <br /> The qla24xx_alloc_purex_item() function may return a pre-allocated item<br /> from a per-adapter pool for small allocations, instead of dynamically<br /> allocating memory with kzalloc().<br /> <br /> An error handling path in qla2xxx_process_purls_iocb() incorrectly uses<br /> kfree() to release the item. If the item was from the pre-allocated<br /> pool, calling kfree() on it is a bug that can lead to memory corruption.<br /> <br /> Fix this by using the correct deallocation function,<br /> qla24xx_free_purex_item(), which properly handles both dynamically<br /> allocated and pre-allocated items.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-68742
Publication date:
24/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bpf: Fix invalid prog-&gt;stats access when update_effective_progs fails<br /> <br /> Syzkaller triggers an invalid memory access issue following fault<br /> injection in update_effective_progs. The issue can be described as<br /> follows:<br /> <br /> __cgroup_bpf_detach<br /> update_effective_progs<br /> compute_effective_progs<br /> bpf_prog_array_alloc items[index] = &amp;dummy_bpf_prog.prog<br /> <br /> ---softirq start---<br /> __do_softirq<br /> ...<br /> __cgroup_bpf_run_filter_skb<br /> __bpf_prog_run_save_cb<br /> bpf_prog_run<br /> stats = this_cpu_ptr(prog-&gt;stats)<br /> /* invalid memory access */<br /> flags = u64_stats_update_begin_irqsave(&amp;stats-&gt;syncp)<br /> ---softirq end---<br /> <br /> static_branch_dec(&amp;cgroup_bpf_enabled_key[atype])<br /> <br /> The reason is that fault injection caused update_effective_progs to fail<br /> and then changed the original prog into dummy_bpf_prog.prog in<br /> purge_effective_progs. Then a softirq came, and accessing the members of<br /> dummy_bpf_prog.prog in the softirq triggers invalid mem access.<br /> <br /> To fix it, skip updating stats when stats is NULL.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-68743
Publication date:
24/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mshv: Fix create memory region overlap check<br /> <br /> The current check is incorrect; it only checks if the beginning or end<br /> of a region is within an existing region. This doesn&amp;#39;t account for<br /> userspace specifying a region that begins before and ends after an<br /> existing region.<br /> <br /> Change the logic to a range intersection check against gfns and uaddrs<br /> for each region.<br /> <br /> Remove mshv_partition_region_by_uaddr() as it is no longer used.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-68744
Publication date:
24/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bpf: Free special fields when update [lru_,]percpu_hash maps<br /> <br /> As [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing<br /> calls to &amp;#39;bpf_obj_free_fields()&amp;#39; in &amp;#39;pcpu_copy_value()&amp;#39; could cause the<br /> memory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the<br /> map gets freed.<br /> <br /> Fix this by calling &amp;#39;bpf_obj_free_fields()&amp;#39; after<br /> &amp;#39;copy_map_value[,_long]()&amp;#39; in &amp;#39;pcpu_copy_value()&amp;#39;.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-68745
Publication date:
24/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: qla2xxx: Clear cmds after chip reset<br /> <br /> Commit aefed3e5548f ("scsi: qla2xxx: target: Fix offline port handling<br /> and host reset handling") caused two problems:<br /> <br /> 1. Commands sent to FW, after chip reset got stuck and never freed as FW<br /> is not going to respond to them anymore.<br /> <br /> 2. BUG_ON(cmd-&gt;sg_mapped) in qlt_free_cmd(). Commit 26f9ce53817a<br /> ("scsi: qla2xxx: Fix missed DMA unmap for aborted commands")<br /> attempted to fix this, but introduced another bug under different<br /> circumstances when two different CPUs were racing to call<br /> qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in<br /> dma_unmap_sg_attrs().<br /> <br /> So revert "scsi: qla2xxx: Fix missed DMA unmap for aborted commands" and<br /> partially revert "scsi: qla2xxx: target: Fix offline port handling and<br /> host reset handling" at __qla2x00_abort_all_cmds.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-68746
Publication date:
24/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> spi: tegra210-quad: Fix timeout handling<br /> <br /> When the CPU that the QSPI interrupt handler runs on (typically CPU 0)<br /> is excessively busy, it can lead to rare cases of the IRQ thread not<br /> running before the transfer timeout is reached.<br /> <br /> While handling the timeouts, any pending transfers are cleaned up and<br /> the message that they correspond to is marked as failed, which leaves<br /> the curr_xfer field pointing at stale memory.<br /> <br /> To avoid this, clear curr_xfer to NULL upon timeout and check for this<br /> condition when the IRQ thread is finally run.<br /> <br /> While at it, also make sure to clear interrupts on failure so that new<br /> interrupts can be run.<br /> <br /> A better, more involved, fix would move the interrupt clearing into a<br /> hard IRQ handler. Ideally we would also want to signal that the IRQ<br /> thread no longer needs to be run after the timeout is hit to avoid the<br /> extra check for a valid transfer.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025

CVE-2025-68747
Publication date:
24/12/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/panthor: Fix UAF on kernel BO VA nodes<br /> <br /> If the MMU is down, panthor_vm_unmap_range() might return an error.<br /> We expect the page table to be updated still, and if the MMU is blocked,<br /> the rest of the GPU should be blocked too, so no risk of accessing<br /> physical memory returned to the system (which the current code doesn&amp;#39;t<br /> cover for anyway).<br /> <br /> Proceed with the rest of the cleanup instead of bailing out and leaving<br /> the va_node inserted in the drm_mm, which leads to UAF when other<br /> adjacent nodes are removed from the drm_mm tree.
Severity CVSS v4.0: Pending analysis
Last modification:
24/12/2025
Subscribe to Vulnerabilities