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

Publication date:
04/09/2025
In onCreate of UninstallerActivity.java, there is a possible way to uninstall a different user's app due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2025-0077

Publication date:
04/09/2025
In multiple functions of UserController.java, there is a possible lock screen bypass due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2024-49739

Publication date:
04/09/2025
In MMapVAccess of pmr_os.c, there is a possible out of bounds write due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2023-35657

Publication date:
04/09/2025
In bta_av_config_ind of bta_av_aact.cc, there is a possible out of bounds read due to type confusion. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2025-9636

Publication date:
04/09/2025
pgAdmin
Severity CVSS v4.0: Pending analysis
Last modification:
11/09/2025

CVE-2025-38729

Publication date:
04/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ALSA: usb-audio: Validate UAC3 power domain descriptors, too<br /> <br /> UAC3 power domain descriptors need to be verified with its variable<br /> bLength for avoiding the unexpected OOB accesses by malicious<br /> firmware, too.
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2025-38730

Publication date:
04/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> io_uring/net: commit partial buffers on retry<br /> <br /> Ring provided buffers are potentially only valid within the single<br /> execution context in which they were acquired. io_uring deals with this<br /> and invalidates them on retry. But on the networking side, if<br /> MSG_WAITALL is set, or if the socket is of the streaming type and too<br /> little was processed, then it will hang on to the buffer rather than<br /> recycle or commit it. This is problematic for two reasons:<br /> <br /> 1) If someone unregisters the provided buffer ring before a later retry,<br /> then the req-&gt;buf_list will no longer be valid.<br /> <br /> 2) If multiple sockers are using the same buffer group, then multiple<br /> receives can consume the same memory. This can cause data corruption<br /> in the application, as either receive could land in the same<br /> userspace buffer.<br /> <br /> Fix this by disallowing partial retries from pinning a provided buffer<br /> across multiple executions, if ring provided buffers are used.
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2025-57576

Publication date:
04/09/2025
PHPGurukul Online Shopping Portal 2.1 is vulnerable to Cross Site Scripting (XSS) in /admin/updateorder.php.
Severity CVSS v4.0: Pending analysis
Last modification:
10/09/2025

CVE-2025-38723

Publication date:
04/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> LoongArch: BPF: Fix jump offset calculation in tailcall<br /> <br /> The extra pass of bpf_int_jit_compile() skips JIT context initialization<br /> which essentially skips offset calculation leaving out_offset = -1, so<br /> the jmp_offset in emit_bpf_tail_call is calculated by<br /> <br /> "#define jmp_offset (out_offset - (cur_offset))"<br /> <br /> is a negative number, which is wrong. The final generated assembly are<br /> as follow.<br /> <br /> 54: bgeu $a2, $t1, -8 # 0x0000004c<br /> 58: addi.d $a6, $s5, -1<br /> 5c: bltz $a6, -16 # 0x0000004c<br /> 60: alsl.d $t2, $a2, $a1, 0x3<br /> 64: ld.d $t2, $t2, 264<br /> 68: beq $t2, $zero, -28 # 0x0000004c<br /> <br /> Before apply this patch, the follow test case will reveal soft lock issues.<br /> <br /> cd tools/testing/selftests/bpf/<br /> ./test_progs --allow=tailcalls/tailcall_bpf2bpf_1<br /> <br /> dmesg:<br /> watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [test_progs:25056]
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2025-38724

Publication date:
04/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm()<br /> <br /> Lei Lu recently reported that nfsd4_setclientid_confirm() did not check<br /> the return value from get_client_locked(). a SETCLIENTID_CONFIRM could<br /> race with a confirmed client expiring and fail to get a reference. That<br /> could later lead to a UAF.<br /> <br /> Fix this by getting a reference early in the case where there is an<br /> extant confirmed client. If that fails then treat it as if there were no<br /> confirmed client found at all.<br /> <br /> In the case where the unconfirmed client is expiring, just fail and<br /> return the result from get_client_locked().
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2025-38725

Publication date:
04/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: usb: asix_devices: add phy_mask for ax88772 mdio bus<br /> <br /> Without setting phy_mask for ax88772 mdio bus, current driver may create<br /> at most 32 mdio phy devices with phy address range from 0x00 ~ 0x1f.<br /> DLink DUB-E100 H/W Ver B1 is such a device. However, only one main phy<br /> device will bind to net phy driver. This is creating issue during system<br /> suspend/resume since phy_polling_mode() in phy_state_machine() will<br /> directly deference member of phydev-&gt;drv for non-main phy devices. Then<br /> NULL pointer dereference issue will occur. Due to only external phy or<br /> internal phy is necessary, add phy_mask for ax88772 mdio bus to workarnoud<br /> the issue.
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025

CVE-2025-38726

Publication date:
04/09/2025
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: ftgmac100: fix potential NULL pointer access in ftgmac100_phy_disconnect<br /> <br /> After the call to phy_disconnect() netdev-&gt;phydev is reset to NULL.<br /> So fixed_phy_unregister() would be called with a NULL pointer as argument.<br /> Therefore cache the phy_device before this call.
Severity CVSS v4.0: Pending analysis
Last modification:
05/09/2025