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

Publication date:
22/08/2025
D-Link DIR-619L 2.06B01 is vulnerable to Buffer Overflow in the formWlanSetup function via the parameter f_wds_wepKey.
Severity CVSS v4.0: Pending analysis
Last modification:
26/09/2025

CVE-2025-55602

Publication date:
22/08/2025
D-Link DIR-619L 2.06B01 is vulnerable to Buffer Overflow in the formSysCmd function via the submit-url parameter.
Severity CVSS v4.0: Pending analysis
Last modification:
26/09/2025

CVE-2025-55603

Publication date:
22/08/2025
Tenda AX3 V16.03.12.10_CN is vulnerable to Buffer Overflow in the fromSetSysTime function via the ntpServer parameter.
Severity CVSS v4.0: Pending analysis
Last modification:
26/09/2025

CVE-2025-55605

Publication date:
22/08/2025
Tenda AX3 V16.03.12.10_CN is vulnerable to Buffer Overflow in the saveParentControlInfo function via the deviceName parameter.
Severity CVSS v4.0: Pending analysis
Last modification:
26/09/2025

CVE-2025-55606

Publication date:
22/08/2025
Tenda AX3 V16.03.12.10_CN is vulnerable to Buffer Overflow in the fromAdvSetMacMtuWan function via the serverName parameter.
Severity CVSS v4.0: Pending analysis
Last modification:
26/09/2025

CVE-2025-55611

Publication date:
22/08/2025
D-Link DIR-619L 2.06B01 is vulnerable to Buffer Overflow in the formLanguageChange function via the nextPage parameter.
Severity CVSS v4.0: Pending analysis
Last modification:
26/09/2025

CVE-2025-51605

Publication date:
22/08/2025
An issue was discovered in Shopizer 3.2.7. The server's CORS implementation reflects the client-supplied Origin header verbatim into Access-Control-Allow-Origin without any whitelist validation, while also enabling Access-Control-Allow-Credentials: true. This allows any malicious origin to make authenticated cross-origin requests and read sensitive responses.
Severity CVSS v4.0: Pending analysis
Last modification:
12/09/2025

CVE-2025-52094

Publication date:
22/08/2025
Insecure Permissions vulnerability in PDQ Smart Deploy V.3.0.2040 allows a local attacker to execute arbtirary code via the \HKLM\SYSTEM\Setup\SmartDeploy component
Severity CVSS v4.0: Pending analysis
Last modification:
27/01/2026

CVE-2025-52095

Publication date:
22/08/2025
An issue in PDQ Smart Deploy V.3.0.2040 allows an attacker to escalate privileges via the Credential encryption routines in SDCommon.dll
Severity CVSS v4.0: Pending analysis
Last modification:
27/01/2026

CVE-2025-53363

Publication date:
22/08/2025
dpanel is an open source server management panel written in Go. In versions 1.2.0 through 1.7.2, dpanel allows authenticated users to read arbitrary files from the server via the /api/app/compose/get-from-uri API endpoint. The vulnerability exists in the GetFromUri function in app/application/http/controller/compose.go, where the uri parameter is passed directly to os.ReadFile without proper validation or access control. A logged-in attacker can exploit this flaw to read sensitive files from the host system, leading to information disclosure. No patched version is available as of this writing.
Severity CVSS v4.0: MEDIUM
Last modification:
29/04/2026

CVE-2025-38674

Publication date:
22/08/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Revert "drm/prime: Use dma_buf from GEM object instance"<br /> <br /> This reverts commit f83a9b8c7fd0557b0c50784bfdc1bbe9140c9bf8.<br /> <br /> The dma_buf field in struct drm_gem_object is not stable over the<br /> object instance&amp;#39;s lifetime. The field becomes NULL when user space<br /> releases the final GEM handle on the buffer object. This resulted<br /> in a NULL-pointer deref.<br /> <br /> Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on<br /> GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:<br /> Acquire internal references on GEM handles") only solved the problem<br /> partially. They especially don&amp;#39;t work for buffer objects without a DRM<br /> framebuffer associated.<br /> <br /> Hence, this revert to going back to using .import_attach-&gt;dmabuf.<br /> <br /> v3:<br /> - cc stable
Severity CVSS v4.0: Pending analysis
Last modification:
25/11/2025

CVE-2025-38675

Publication date:
22/08/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> xfrm: state: initialize state_ptrs earlier in xfrm_state_find<br /> <br /> In case of preemption, xfrm_state_look_at will find a different<br /> pcpu_id and look up states for that other CPU. If we matched a state<br /> for CPU2 in the state_cache while the lookup started on CPU1, we will<br /> jump to "found", but the "best" state that we got will be ignored and<br /> we will enter the "acquire" block. This block uses state_ptrs, which<br /> isn&amp;#39;t initialized at this point.<br /> <br /> Let&amp;#39;s initialize state_ptrs just after taking rcu_read_lock. This will<br /> also prevent a possible misuse in the future, if someone adjusts this<br /> function.
Severity CVSS v4.0: Pending analysis
Last modification:
25/11/2025