CVE Vulnerability Catalog

Discourse is an open-source discussion platform. Prior to 2026.9.0, 2026.8.1, 2026.7.3, and 2026.1.9, sites with secure uploads enabled did not reconcile existing upload security metadata when a previously public category became read-restricted or when category permissions changed during a bulk import. Media and attachments uploaded while the category was public retained a public accessibility flag and remained reachable by anonymous users through their short upload URLs, including uploads associated with deleted topics. This issue is fixed in versions 2026.9.0, 2026.8.1, 2026.7.3, and 2026.1.9.

Discourse is an open-source discussion platform. Prior to 2026.9.0, 2026.8.1, 2026.7.3, and 2026.1.9, MessageBus audience calculation could deliver messages from a read-restricted category chat channel to an authenticated user who could view the category but was not allowed to use Chat under the site's group restrictions. The publication path bounded events by category visibility without also enforcing Chat eligibility, exposing live and recent message content available in the MessageBus backlog. The issue does not permit retrieval of the channel's full history through the Chat API and does not permit message creation or modification. This issue is fixed in versions 2026.9.0, 2026.8.1, 2026.7.3, and 2026.1.9.

The SFTP module of Progress MOVEit Transfer contains an incorrect implementation of the authentication algorithm. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

The Custom Reports module of Progress MOVEit Transfer is vulnerable to SQL injection due to improper neutralization of special elements in SQL commands. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

Progress MOVEit Transfer contains an insecure storage of sensitive information vulnerability. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

Progress MOVEit Transfer contains an improper handling of Unicode encoding vulnerability. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

Progress MOVEit Transfer contains an insufficient session expiration vulnerability. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

The Client Certificates module of Progress MOVEit Transfer contains an incorrect authorization vulnerability. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

The LDAP module of Progress MOVEit Transfer is vulnerable to LDAP injection due to improper neutralization of special elements in LDAP queries. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

The OIDC module of Progress MOVEit Transfer contains an authentication bypass by capture-replay vulnerability. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

The Ad Hoc module of Progress MOVEit Transfer contains a cross-site scripting (XSS) vulnerability due to improper neutralization of input during web page generation. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

The LDAP module of Progress MOVEit Transfer contains a missing critical step in authentication vulnerability. The issue affects versions before 2025.1.6 and from 2026.0.0 before 2026.0.4.

Authentication bypass using an alternate path or channel vulnerability in Progress MOVEit Transfer. This issue affects MOVEit Transfer: before 2025.1.6 and from 2026.0.0 before 2026.0.4.

Incorrect Permission Assignment for Critical Resource vulnerability in Progress MOVEit Transfer. This issue affects MOVEit Transfer: before 2025.1.6 and from 2026.0.0 before 2026.0.4.

A flaw was found in DPDK lib/vhost. Memory size is not adequately validated before mmap during vhost memory-region setup, which can lead to a host crash or memory corruption.

Dokku before 0.38.25 allows a user with app-level access and remote SSH to store arbitrary strings via docker-options, which are later concatenated into DOCKER_ARGS and processed by Bash eval, leading to arbitrary command execution with dokku user privileges.

In VeraCrypt 1.26.29 and earlier, selected metadata IOCTL handlers in the Windows veracrypt.sys driver accept caller-supplied object-manager and device paths broader than supported VeraCrypt workflows require. A local user who can open the intentionally user-accessible \\.\VeraCrypt device can make the driver perform kernel-context symbolic-link or disk-device lookups outside the intended path scope. This can disclose low-sensitivity drive-letter targets, partition information, disk geometry, GPT or MBR state, and limited object-manager path metadata.

Dell Terraform Provider for Redfish, versions 1.1.0 through 1.6.1, contains an Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the redfish_certificate resource component. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to information exposure.

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, the optimized AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl matches the textual prefixes of symbolic data, sequence, and value body descriptors without verifying their encoded symbol lengths. An authenticated AMQP 1.0 publisher with write permission can submit a well-formed unknown descriptor that begins with a registered body descriptor, and RabbitMQ misclassifies and stores the bytes as a standard body section. Strict AMQP 1.0 consumers can terminate while decoding the stored entry. For bodies misclassified as data, AMQP 0-9-1 or other cross-protocol conversion performs full body decoding and can terminate the consumer protocol process, with acknowledgement-required delivery permitting repeated failures. Sequence and value classifications are normally transported as opaque encoded payloads on that conversion path. The broker remains alive, and the issue does not bypass routing or authorization. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, deps/amqp10_common/src/amqp10_binary_parser.erl materializes each element of AMQP 1.0 arrays whose shared constructor has zero width, while limiting only the number of elements in each array and not the aggregate arrays in a frame. After completing SASL authentication, a low-privilege client can send an ordinary frame containing many individually permitted arrays, causing a small frame to expand into a very large reader-process heap before later frame validation or authorization. Because deps/rabbit/src/rabbit_amqp_reader.erl clears the pre-authentication max_heap_size guard after login, repeated or concurrent frames can trigger the node-wide memory alarm, block publishers, or exhaust broker memory. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.