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-2021-47997

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2021-47998

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2021-47999

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2021-48000

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2021-48001

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2021-48002

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2021-48003

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2021-48004

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2021-48005

Publication date:
27/08/2026
Rejected reason: This CVE ID has been rejected.
Severity CVSS v4.0: Pending analysis
Last modification:
27/08/2026

CVE-2026-81743

Publication date:
27/08/2026
Affected versions of Flowintel allow the LOG_FILE configuration value to be modified through system settings without restricting it to a filename inside the intended log directory.<br /> <br /> <br /> Because the application constructs the log destination from this configurable value, an administrator could set LOG_FILE to an arbitrary filesystem path. Since attackers can influence logged content, this enables controlled data to be written into unintended files. The upstream commit specifically describes an exploitation chain in which an attacker injects a template into a chosen file and subsequently abuses application rendering behavior to execute code.<br /> <br /> The patch removes LOG_FILE from the web-editable settings, introduces validate_log_file_name() to reject absolute paths, traversal, Windows paths, null bytes, and directory components, and centralizes log path construction through resolve_log_file_path().<br /> <br /> Version impacted: &gt;=3.3.0
Severity CVSS v4.0: HIGH
Last modification:
28/08/2026

CVE-2026-81753

Publication date:
27/08/2026
Affected versions of Flowintel render Mermaid blocks contained in stored case notes without sufficiently neutralizing attacker-controlled markup. Because Mermaid note content is persisted and later rendered for other users, an attacker with permission to create or edit a note could store a crafted Mermaid payload that results in JavaScript execution when another user views the affected case note.<br /> <br /> The patch adds explicit Mermaid detection and HTML escaping around the token content before the generated Mermaid wrapper is returned. It also moves the wrapping logic earlier in page initialization so Markdown instances are protected consistently.<br /> <br /> Version impacted &gt;= 3.3.0
Severity CVSS v4.0: MEDIUM
Last modification:
28/08/2026

CVE-2026-81814

Publication date:
27/08/2026
Affected versions of Flowintel render calendar event titles using innerHTML. Because those titles are derived from case titles, a user able to create or modify a case title could store HTML or script-capable content that is later interpreted by the browser when another user views the calendar.<br /> <br /> <br /> The fix changes:<br /> <br /> <br /> titleEl.innerHTML = arg.event.title<br /> <br /> <br /> to:<br /> <br /> <br /> titleEl.textContent = arg.event.title || &amp;#39;&amp;#39;<br /> <br /> and similarly stops using innerHTML for the static download icon.<br /> <br /> Version impacted =&gt;3.3.0
Severity CVSS v4.0: MEDIUM
Last modification:
28/08/2026