Vulnerabilidades

Con el objetivo de informar, advertir y ayudar a los profesionales sobre las últimas vulnerabilidades de seguridad en sistemas tecnológicos, ponemos a disposición de los usuarios interesados en esta información una base de datos con información en castellano sobre cada una de las últimas vulnerabilidades documentadas y conocidas.

Este repositorio con más de 75.000 registros esta basado en la información de NVD (National Vulnerability Database) – en función de un acuerdo de colaboración – por el cual desde INCIBE realizamos la traducción al castellano de la información incluida. En ocasiones este listado mostrará vulnerabilidades que aún no han sido traducidas debido a que se recogen en el transcurso del tiempo en el que el equipo de INCIBE realiza el proceso de traducción.

Se emplea el estándar de nomenclatura de vulnerabilidades CVE (Common Vulnerabilities and Exposures), con el fin de facilitar el intercambio de información entre diferentes bases de datos y herramientas. Cada una de las vulnerabilidades recogidas enlaza a diversas fuentes de información así como a parches disponibles o soluciones aportadas por los fabricantes y desarrolladores. Es posible realizar búsquedas avanzadas teniendo la opción de seleccionar diferentes criterios como el tipo de vulnerabilidad, fabricante, tipo de impacto entre otros, con el fin de acortar los resultados.

Mediante suscripción RSS o Boletines podemos estar informados diariamente de las últimas vulnerabilidades incorporadas al repositorio.

CVE-2026-9250

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Gravedad: Pendiente de análisis

Última modificación:

26/08/2026

CVE-2026-9252

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Gravedad: Pendiente de análisis

Última modificación:

26/08/2026

CVE-2026-80200

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Kimai before 2.53.0 contains an open redirect vulnerability in the SAML authentication success handler that accepts unvalidated RelayState POST parameters as redirect destinations. Attackers with IdP access can supply malicious RelayState values to redirect authenticated users to attacker-controlled URLs for credential theft or phishing attacks.

Gravedad: Pendiente de análisis

Última modificación:

26/08/2026

CVE-2026-80202

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Kimai before 2.56.0 does not enforce team-membership checks in TimesheetVoter::voteOnAttribute(), which maps permissions only to own_timesheet or other_timesheet. As a result, any authenticated user with ROLE_TEAMLEAD (or a role holding edit_other_timesheet/delete_other_timesheet) can read, modify, and permanently delete timesheets belonging to any user system-wide via the API, regardless of team membership. Timesheet IDs are sequential integers and trivially enumerable. ROLE_USER accounts are correctly restricted. (Note: the maintainers characterize this behavior as matching the documented permission model.)

Gravedad CVSS v4.0: CRÍTICA

Última modificación:

26/08/2026

CVE-2026-80196

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Kimai before 2.58.0 contains an authentication bypass vulnerability where password reset links remain valid after password changes because the LoginLink signature covers only the user id, not the password hash. Attackers who intercept or cache a password reset link can use it up to 2 additional times within a 1-hour window to log in as the user even after the legitimate user has changed their password.

Gravedad CVSS v4.0: ALTA

Última modificación:

26/08/2026

CVE-2026-80201

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Kimai before 2.53.0 fails to block sensitive User methods in the Twig invoice template sandbox, allowing admins to call getApiToken() and getPlainApiToken() methods. Attackers with template creation permissions can embed these method calls in invoice templates to leak hashed API tokens in rendered invoice output.

Gravedad CVSS v4.0: BAJA

Última modificación:

26/08/2026

CVE-2026-80199

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Kimai before 2.54.0 contains a timing oracle vulnerability in TokenAuthenticator that allows unauthenticated attackers to enumerate valid usernames via X-AUTH-USER header. Attackers can measure response time differences when the password hasher runs only for existing users, enabling username enumeration with no login throttling protection.

Gravedad CVSS v4.0: MEDIA

Última modificación:

26/08/2026

CVE-2026-80197

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Kimai before 2.57.0 contains an improper authorization vulnerability in the favorite timesheet add and remove endpoints that allows authenticated users to manipulate other users&#39; bookmarks. Attackers can add or remove timesheet entries from another user&#39;s favorite list by referencing their timesheet identifier, enabling cross-user business-state tampering without administrative privileges.

Gravedad CVSS v4.0: ALTA

Última modificación:

26/08/2026

CVE-2026-80198

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Kimai versions before 2.56.0 fail to restrict the config() Twig function in sandboxed invoice and export templates, allowing administrators to access arbitrary configuration keys. Attackers with admin privileges can upload malicious templates to exfiltrate server-wide secrets including LDAP bind passwords and SAML private keys into invoice or export documents accessible to lower-privileged users.

Gravedad CVSS v4.0: ALTA

Última modificación:

26/08/2026

CVE-2026-80189

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** LeafWiki extracts an uploaded ZIP archive without limiting how much data it will write. ZipExtractor.ExtractToDir in internal/importer/zip_extractor.go opens each entry and copies it to the destination with io.Copy, which runs to the end of the decompressed stream, so only the size of the uploaded archive is bounded and the size it expands to is not. The import route that reaches this code requires the Editor or Admin role, and the upload itself is capped at 500 MiB compressed. Because a ZIP entry can compress at a very high ratio, an archive well inside that cap can expand to hundreds of gigabytes as it is written out. The extraction directory defaults to a location under the operating system temporary directory, so the written data consumes the disk backing that path, which on a tmpfs-backed temporary directory is memory. A user holding the Editor role can therefore exhaust the storage the service depends on and keep it from serving, using far more resource than the upload limit alone would permit.

Gravedad CVSS v4.0: ALTA

Última modificación:

26/08/2026

CVE-2026-80195

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** Kimai before 2.63.0 contains a business logic / improper authorization vulnerability in the team update API endpoint (PATCH /api/teams/{id}), which removes all existing team members before validating the submitted replacement member list. An authenticated teamlead (or other user) with permission to edit a team can submit a malformed members payload; although Kimai returns a validation error, the existing membership rows have already been deleted. This bypasses the dedicated member-removal endpoint&#39;s protection against removing teamleaders and can leave a team with no members or teamleaders, disrupting team-based access control.

Gravedad CVSS v4.0: ALTA

Última modificación:

26/08/2026

CVE-2026-80191

Fecha de publicación:

26/08/2026

Idioma:

Inglés

*** Pendiente de traducción *** GROWI applies its page-viewer permission check to attachment requests only when the request carries an authenticated user. retrieveAttachmentFromIdParam in apps/app/src/server/routes/attachment/get.ts guards the check with a condition requiring the user to be non-null, so a request that carries no session skips the check entirely and the handler returns the file. The routes reached this way, /attachment/:id and /download/:id, take the attachment identifier from the path, so an unauthenticated caller who has an attachment identifier receives the file regardless of whether the page owning it is private and regardless of whether that caller would be permitted to view the page. Identifiers can be retained by a user whose access was later removed, or recovered from anywhere the identifier was previously exposed. Version 8.0.2 runs the check for authenticated and unauthenticated requests alike, skipping it only where a valid share link has already bound the requested file to that link&#39;s page.

Gravedad CVSS v4.0: ALTA

Última modificación:

26/08/2026

Suscribirse a Vulnerabilidades