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

Publication date:
11/05/2026
Path traversal vulnerability exists in GROWI v7.5.0 and earlier, which may allow an attacker to execute arbitrary EJS templates on the server when an email server is running in GROWI.
Severity CVSS v4.0: HIGH
Last modification:
12/05/2026

CVE-2026-40636

Publication date:
11/05/2026
Dell ECS versions 3.8.1.0 through 3.8.1.7 and Dell ObjectScale versions prior to 4.3.0.0, contains a use of hard-coded credentials vulnerability. An unauthenticated attacker with local access could potentially exploit this vulnerability, leading to filesystem access for attacker.
Severity CVSS v4.0: Pending analysis
Last modification:
12/05/2026

CVE-2026-35157

Publication date:
11/05/2026
Dell ECS versions 3.8.1.0 through 3.8.1.7 and Dell ObjectScale versions prior to 4.3.0.0, contains an improper neutralization of formula elements in a CSV File vulnerability in the UI. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to remote execution.
Severity CVSS v4.0: Pending analysis
Last modification:
12/05/2026

CVE-2026-26946

Publication date:
11/05/2026
Dell ECS versions 3.8.1.0 through 3.8.1.7 and Dell ObjectScale versions prior to 4.3.0.0, contains an improper privilege management vulnerability in the OS. A high privileged attacker with local access could potentially exploit this vulnerability, leading to elevation of privileges.
Severity CVSS v4.0: Pending analysis
Last modification:
12/05/2026

CVE-2025-43992

Publication date:
11/05/2026
Dell ECS versions 3.8.1.0 through 3.8.1.7 and Dell ObjectScale versions prior to 4.3.0.0, contains an authentication bypass by assumed-immutable data vulnerability in Geo replication. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to unauthorized access to data in transit.
Severity CVSS v4.0: Pending analysis
Last modification:
12/05/2026

CVE-2025-10908

Publication date:
11/05/2026
Due to a lack of user account state validation during authentication, locked user accounts can be successfully authenticated using Magic Link or Pass Key methods. This bypasses the intended security control that should prevent access to accounts that have been locked.<br /> <br /> This vulnerability may allow unauthorized access to applications and sensitive data associated with accounts that should have been restricted via the account lock mechanism. It also undermines the effectiveness of the account lock mechanism intended to prevent further login attempts.
Severity CVSS v4.0: Pending analysis
Last modification:
13/05/2026

CVE-2025-8154

Publication date:
11/05/2026
In Webhook API invocations, the component accepts user-supplied input for HTTP request headers without sufficient validation or sanitization, allowing these headers to be injected into HTTP responses.<br /> <br /> By exploiting this vulnerability, a malicious actor can inject or overwrite arbitrary HTTP response headers. This can lead to various adverse effects, including the manipulation of browser caching, alteration of security-related headers, and the injection of sensitive information such as cookie values, potentially enabling session hijacking or other malicious activities.
Severity CVSS v4.0: Pending analysis
Last modification:
13/05/2026

CVE-2024-0391

Publication date:
11/05/2026
The check user account lock states feature within the email OTP flow fails to validate user input, allowing an attacker to infer the existence of registered user accounts.<br /> <br /> The discovery of valid usernames can increase the risk of brute-force and social engineering attacks. Attackers can leverage this information to craft targeted phishing campaigns or other malicious activities aimed at tricking users into divulging sensitive data, potentially damaging the organization&amp;#39;s reputation and leading to regulatory non-compliance and financial consequences.
Severity CVSS v4.0: Pending analysis
Last modification:
13/05/2026

CVE-2026-43826

Publication date:
11/05/2026
The OpenSearch logging provider, when configured with a `host` URL that embeds credentials (for example `https://user:password@server.example.com:9200`), wrote the full host URL — including the embedded credentials — into task logs. Any user with task-log read permission could harvest the backend credentials. Users are advised to upgrade to `apache-airflow-providers-opensearch` 1.9.1 or later and, as a defense-in-depth measure, configure the backend credentials via a secret backend rather than embedding them in the `[opensearch] host` URL.
Severity CVSS v4.0: Pending analysis
Last modification:
13/05/2026

CVE-2026-41018

Publication date:
11/05/2026
The Elasticsearch logging provider, when configured with a `host` URL that embeds credentials (for example `https://user:password@server.example.com:9200`), wrote the full host URL — including the embedded credentials — into task logs. Any user with task-log read permission could harvest the backend credentials. Users are advised to upgrade to `apache-airflow-providers-elasticsearch` 6.5.3 or later and, as a defense-in-depth measure, configure the backend credentials via a secret backend rather than embedding them in the `[elasticsearch] host` URL.
Severity CVSS v4.0: Pending analysis
Last modification:
13/05/2026

CVE-2026-43500

Publication date:
11/05/2026
In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present<br /> <br /> The DATA-packet handler in rxrpc_input_call_event() and the RESPONSE<br /> handler in rxrpc_verify_response() copy the skb to a linear one before<br /> calling into the security ops only when skb_cloned() is true. An skb<br /> that is not cloned but still carries externally-owned paged fragments<br /> (e.g. SKBFL_SHARED_FRAG set by splice() into a UDP socket via<br /> __ip_append_data, or a chained skb_has_frag_list()) falls through to<br /> the in-place decryption path, which binds the frag pages directly into<br /> the AEAD/skcipher SGL via skb_to_sgvec().<br /> <br /> Extend the gate to also unshare when skb_has_frag_list() or<br /> skb_has_shared_frag() is true. This catches the splice-loopback vector<br /> and other externally-shared frag sources while preserving the<br /> zero-copy fast path for skbs whose frags are kernel-private (e.g. NIC<br /> page_pool RX, GRO). The OOM/trace handling already in place is reused.
Severity CVSS v4.0: Pending analysis
Last modification:
14/05/2026

CVE-2026-5084

Publication date:
11/05/2026
WebDyne::Session versions through 2.075 for Perl generates the session id insecurely.<br /> <br /> The session handler generates the session id from an MD5 hash seeded with a call to the built-in rand() function. The rand function is passed a maximum value based on the process id, the epoch time and the reference address of the object, but this information will have no effect on the overall quality of the seed of the message digest.<br /> <br /> The rand function is seeded by 32-bits and is predictable. It is considered unsuitable for cryptographic purposes.<br /> <br /> Predictable session ids could allow an attacker to gain access to systems.<br /> <br /> Note that WebDyne::Session versions 1.042 and earlier appear to be in separate distributions from WebDyne.
Severity CVSS v4.0: Pending analysis
Last modification:
12/05/2026