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

Publication date:
21/01/2026
A flaw was found in glib. Missing validation of offset and count parameters in the g_buffered_input_stream_peek() function can lead to an integer overflow during length calculation. When specially crafted values are provided, this overflow results in an incorrect size being passed to memcpy(), triggering a buffer overflow. This can cause application crashes, leading to a Denial of Service (DoS).
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2026-0663

Publication date:
21/01/2026
Denial-of-service vulnerability in M-Files Server versions before 26.1.15632.3 allows an authenticated attacker with vault administrator privileges to crash the M-Files Server process by calling a vulnerable API endpoint.
Severity CVSS v4.0: MEDIUM
Last modification:
21/01/2026

CVE-2026-24016

Publication date:
21/01/2026
The installer of ServerView Agents for Windows provided by Fsas Technologies Inc. may insecurely load Dynamic Link Libraries. Arbitrary code may be executed with the administrator privilege when the installer is executed.
Severity CVSS v4.0: HIGH
Last modification:
21/01/2026

CVE-2026-22976

Publication date:
21/01/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset<br /> <br /> `qfq_class-&gt;leaf_qdisc-&gt;q.qlen &gt; 0` does not imply that the class<br /> itself is active.<br /> <br /> Two qfq_class objects may point to the same leaf_qdisc. This happens<br /> when:<br /> <br /> 1. one QFQ qdisc is attached to the dev as the root qdisc, and<br /> <br /> 2. another QFQ qdisc is temporarily referenced (e.g., via qdisc_get()<br /> / qdisc_put()) and is pending to be destroyed, as in function<br /> tc_new_tfilter.<br /> <br /> When packets are enqueued through the root QFQ qdisc, the shared<br /> leaf_qdisc-&gt;q.qlen increases. At the same time, the second QFQ<br /> qdisc triggers qdisc_put and qdisc_destroy: the qdisc enters<br /> qfq_reset() with its own q-&gt;q.qlen == 0, but its class&amp;#39;s leaf<br /> qdisc-&gt;q.qlen &gt; 0. Therefore, the qfq_reset would wrongly deactivate<br /> an inactive aggregate and trigger a null-deref in qfq_deactivate_agg:<br /> <br /> [ 0.903172] BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> [ 0.903571] #PF: supervisor write access in kernel mode<br /> [ 0.903860] #PF: error_code(0x0002) - not-present page<br /> [ 0.904177] PGD 10299b067 P4D 10299b067 PUD 10299c067 PMD 0<br /> [ 0.904502] Oops: Oops: 0002 [#1] SMP NOPTI<br /> [ 0.904737] CPU: 0 UID: 0 PID: 135 Comm: exploit Not tainted 6.19.0-rc3+ #2 NONE<br /> [ 0.905157] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org 04/01/2014<br /> [ 0.905754] RIP: 0010:qfq_deactivate_agg (include/linux/list.h:992 (discriminator 2) include/linux/list.h:1006 (discriminator 2) net/sched/sch_qfq.c:1367 (discriminator 2) net/sched/sch_qfq.c:1393 (discriminator 2))<br /> [ 0.906046] Code: 0f 84 4d 01 00 00 48 89 70 18 8b 4b 10 48 c7 c2 ff ff ff ff 48 8b 78 08 48 d3 e2 48 21 f2 48 2b 13 48 8b 30 48 d3 ea 8b 4b 18 0<br /> <br /> Code starting with the faulting instruction<br /> ===========================================<br /> 0: 0f 84 4d 01 00 00 je 0x153<br /> 6: 48 89 70 18 mov %rsi,0x18(%rax)<br /> a: 8b 4b 10 mov 0x10(%rbx),%ecx<br /> d: 48 c7 c2 ff ff ff ff mov $0xffffffffffffffff,%rdx<br /> 14: 48 8b 78 08 mov 0x8(%rax),%rdi<br /> 18: 48 d3 e2 shl %cl,%rdx<br /> 1b: 48 21 f2 and %rsi,%rdx<br /> 1e: 48 2b 13 sub (%rbx),%rdx<br /> 21: 48 8b 30 mov (%rax),%rsi<br /> 24: 48 d3 ea shr %cl,%rdx<br /> 27: 8b 4b 18 mov 0x18(%rbx),%ecx<br /> ...<br /> [ 0.907095] RSP: 0018:ffffc900004a39a0 EFLAGS: 00010246<br /> [ 0.907368] RAX: ffff8881043a0880 RBX: ffff888102953340 RCX: 0000000000000000<br /> [ 0.907723] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000<br /> [ 0.908100] RBP: ffff888102952180 R08: 0000000000000000 R09: 0000000000000000<br /> [ 0.908451] R10: ffff8881043a0000 R11: 0000000000000000 R12: ffff888102952000<br /> [ 0.908804] R13: ffff888102952180 R14: ffff8881043a0ad8 R15: ffff8881043a0880<br /> [ 0.909179] FS: 000000002a1a0380(0000) GS:ffff888196d8d000(0000) knlGS:0000000000000000<br /> [ 0.909572] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 0.909857] CR2: 0000000000000000 CR3: 0000000102993002 CR4: 0000000000772ef0<br /> [ 0.910247] PKRU: 55555554<br /> [ 0.910391] Call Trace:<br /> [ 0.910527] <br /> [ 0.910638] qfq_reset_qdisc (net/sched/sch_qfq.c:357 net/sched/sch_qfq.c:1485)<br /> [ 0.910826] qdisc_reset (include/linux/skbuff.h:2195 include/linux/skbuff.h:2501 include/linux/skbuff.h:3424 include/linux/skbuff.h:3430 net/sched/sch_generic.c:1036)<br /> [ 0.911040] __qdisc_destroy (net/sched/sch_generic.c:1076)<br /> [ 0.911236] tc_new_tfilter (net/sched/cls_api.c:2447)<br /> [ 0.911447] rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)<br /> [ 0.911663] ? __pfx_rtnetlink_rcv_msg (net/core/rtnetlink.c:6861)<br /> [ 0.911894] netlink_rcv_skb (net/netlink/af_netlink.c:2550)<br /> [ 0.912100] netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)<br /> [ 0.912296] ? __alloc_skb (net/core/skbuff.c:706)<br /> [ 0.912484] netlink_sendmsg (net/netlink/af<br /> ---truncated---
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2026-24061

Publication date:
21/01/2026
telnetd in GNU Inetutils through 2.7 allows remote authentication bypass via a "-f root" value for the USER environment variable.
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2025-14559

Publication date:
21/01/2026
A flaw was found in the keycloak-services component of Keycloak. This vulnerability allows the issuance of access and refresh tokens for disabled users, leading to unauthorized use of previously revoked privileges, via a business logic vulnerability in the Token Exchange implementation when a privileged client invokes the token exchange flow.
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2026-1035

Publication date:
21/01/2026
A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse policies. When strict refresh token rotation is enabled, the validation and update of refresh token usage are not performed atomically. This allows concurrent refresh requests to bypass single-use enforcement and issue multiple access tokens from the same refresh token. As a result, Keycloak’s refresh token rotation hardening can be undermined.
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2026-24022

Publication date:
21/01/2026
Rejected reason: Not used
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2026-24023

Publication date:
21/01/2026
Rejected reason: Not used
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2026-24024

Publication date:
21/01/2026
Rejected reason: Not used
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2026-24025

Publication date:
21/01/2026
Rejected reason: Not used
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026

CVE-2026-24026

Publication date:
21/01/2026
Rejected reason: Not used
Severity CVSS v4.0: Pending analysis
Last modification:
21/01/2026