CVE Vulnerability Catalog

Dokploy before version 0.29.13 in the local branch of /docker-container-terminal authenticates with validateRequest but does not authorize the attacker-controlled containerId against the caller's role, organization, or service access before passing it to `docker exec`, allowing any authenticated member to obtain a root shell in arbitrary containers on a self-hosted instance.

Dokploy before version 0.29.13 in its WebSocket handlers (in-app terminals and log streamers) authenticate the session but never authorize it. They establish who the user is via validateRequest() and then proceed without consulting the role/permission model that every tRPC procedure enforces. Any authenticated member can therefore open an interactive shell into any container on the host, including the dokploy container that mounts the Docker socket, and from there obtain root on the host, escaping the application and crossing every tenant boundary.

Metabase allows an unauthenticated attacker to inject arbitrary SQL via a publicly shared card or dashboard that exposes a field-filter (dimension) parameter.

Dokploy before version 0.29.13 in the mariadb.ts, mongo.ts, mysql.ts, postgres.ts, redis.ts, and libsql.ts database service deployment functions pass user-controlled dockerImage fields unquoted into docker pull ${dockerImage} shell commands on the remote-server code path.

Dokploy before version 0.29.13 contains a command injection vulnerability in addHostToKnownHostsCommand, where the domain from user-controlled customGitUrl is interpolated into the ssh-keyscan command without proper quoting. An authenticated user with service deployment permission and an attached SSH key can execute arbitrary commands on the Dokploy host during deployment.

Dokploy before version 0.29.13 contains a command injection vulnerability in the backup.listBackupFiles endpoint, where the search parameter is interpolated into the rclone lsjson command without proper sanitization. An authenticated user with backup:read permission can execute arbitrary commands on the Dokploy host.

Dokploy version 0.29.8 and earlier contains a vulnerability due to lack of verification of destinationId ownership in backup.create, backup.update, and backup.restoreBackupWithLogs endpoints. An authenticated user with backup permissions in one organization can access another organization's S3 credentials, read backup objects, or redirect and poison backups across tenant boundaries.

Dokploy before version 0.29.13 contains a command injection vulnerability in registry credential testing and Docker Swarm cluster management endpoints, where user-controlled values are interpolated into shell commands without proper quoting. The vulnerable remote path uses execAsyncRemote, allowing arbitrary command execution on remote servers.

Dokploy before version 0.29.13 contains a command injection vulnerability in writeTraefikConfigRemote, where user-controlled Traefik configuration is interpolated into an echo command executed via execAsyncRemote. Single quotes in redirect regex, usernames, domains, or middleware configuration can break shell quoting and execute arbitrary commands on remote servers. This is an incomplete fix for CVE-2026-45630.

Dokploy before version 0.29.13 contains a command injection vulnerability in the backup.restoreBackupWithLogs subscription, where databaseName and backupFile fields are interpolated into database restore commands without proper separation from shell syntax. An authenticated user with backup-restore permission can inject operating system commands executed in the Dokploy host context.

The use-reducer-async library contained malicious commits in the default branch between 2026-05-18 and 2026-05-19 that executed remotely controlled code during `npm install`. The code fetched a JavaScript payload from an external server, disabled TLS verification, and executed it with the user's privileges. The attack targeted developer machines, skipping CI and cloud environments.

Jaspersoft JasperReports Server contains an unauthenticated XML External Entity (XXE) vulnerability. Affected versions are from 9.0.0 before HF-9 and from 10.0.0 before HF-10.

The use-context-selector library contained malicious commits that executed remote code during npm install. The code was removed by force-push, but local clones and forks may still contain it, and npm install against an affected checkout will still execute the code.

Metacat versions 2.x through 2.19.1 and all 1.x versions contain an unauthenticated path traversal in the `archiveEntryName` parameter of the `action=read` endpoint in the legacy 1.x API. An attacker can read any file accessible to the Tomcat process by sending a single GET request, as path validation is missing and the permission check is commented out.

The OpenCart v4.2.0.0 extension installer does not validate that extracted paths stay within the intended directory. An attacker can craft a malicious extension with path traversal sequences to write files, such as a PHP web shell, into the webroot.

ReadyEcommerce before 4.5.2 has an unauthenticated SQL injection in the product listing API, where the rating parameter is concatenated into a MySQL HAVING clause without parameterization. Attackers can perform time-based blind SQL injection to extract the full database, including user credentials and admin password hashes.

In the Linux kernel, the xfrm subsystem has a vulnerability where skb->prev becomes stale after async crypto steals a GSO segment. If the last segment is stolen, the head's ->prev pointer is not updated, leading to a write through a dangling pointer (use-after-free) in validate_xmit_skb_list(). The fix repoints skb->prev at the last retained segment before returning.

In the Linux kernel, the SMB client has a vulnerability in the fallocate function that can skip holes when the server returns an allocated range starting before the current offset. This can cause later writes to the skipped area to fail with ENOSPC.

In the Linux kernel on s390 architecture, there is a vulnerability in csum_partial() that on machines without vector facility calculates the checksum from address zero instead of the source buffer. This results in incorrect checksums.