PT-2026-6353 · Rubygems · Decidim+1

Published

2026-02-03

·

Updated

2026-02-03

CVSS v4.0

8.2

High

VectorAV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Impact

Private data exports can lead to data leaks in cases where the UUID generation causes collisions for the generated UUIDs.
The bug was introduced by #13571 and affects Decidim versions 0.30.0 or newer (currently 2025-09-23).
This issue was discovered by running the following spec several times in a row, as it can randomly fail due to this bug:
$ cd decidim-core
$ for i in {1..10}; do bundle exec rspec spec/jobs/decidim/download your data export job spec.rb -e "deletes the" || break ; done
Run the spec as many times as needed to hit a UUID that converts to 0 through .to i.
The UUID to zero conversion does not cause a security issue but the security issue is demonstrated with the following example.
The following code regenerates the issue by assigning a predefined UUID that will generate a collision (example assumes there are already two existing users in the system):
# Create the ZIP buffers to be stored
buffer1 = Zip::OutputStream.write buffer do |out|
 out.put next entry("admin.txt")
 out.write "Hello, admin!"
end
buffer1.rewind
buffer2 = Zip::OutputStream.write buffer do |out|
 out.put next entry("user.txt")
 out.write "Hello, user!"
end
buffer2.rewind

# Create the private exports with a predefined IDs
user1 = Decidim::User.find(1)
export = user1.private exports.build
export.id = "0210ae70-482b-4671-b758-35e13e0097a9"
export.export type = "download your data"
export.file.attach(io: buffer1, filename: "foobar.zip", content type: "application/zip")
export.expires at = Decidim.download your data expiry time.from now
export.metadata = {}
export.save!


user2 = Decidim::User.find(2)
export = user2.private exports.build
export.id = "0210d2df-a0c7-40aa-ad97-2dae5083e3b8"
export.export type = "download your data"
export.file.attach(io: buffer2, filename: "foobar.zip", content type: "application/zip")
export.expires at = Decidim.download your data expiry time.from now
export.metadata = {}
export.save!
Expect to see an error in the situation.
Now, login as user with ID 1, go to /download your data, click "Download file" from the export and expect to see the data that should be attached to user with ID 2. This is an artificially replicated situation with the predefined UUIDs but it can easily happen in real situations.
The reason for the test case failure can be replicated in case you change the export ID to export.id = "e9540f96-9e3d-4abe-8c2a-6c338d85a684". This would return 0 through .to s
After attaching that ID, you can test if the file is available for the export:
user.private exports.last.file.attached?
=> false
user.private exports.last.file.blob
=> nil
Note that this fails with such UUID as shown in the example and could easily lead to collisions in case the UUID starts with a number. E.g. UUID "0210ae70-482b-4671-b758-35e13e0097a9" would convert to 210 through .to s. Therefore, if someone else has a "private" export with the prefixes "00000210", "0000210", "000210", "00210", "0210" or "210", that would cause a collision and the file could be attached to the wrong private export.
Theoretical chance of collision (the reality depends on the UUID generation algorithm):
  • Potential combinations of the UUID first part (8 characters hex): 16^8
  • Potentially colliding character combinations (8 numbers characters in the range of 0-9): 10^8
  • 10^8 / 16^8 ≈ 2.3% (23 / 1000 users)
The root cause is that the class Decidim::PrivateExport defines an ActiveStorage relation to file and the table active storage attachments stores the related record id as bigint which causes the conversion to happen.

Workarounds

Fully disable the private exports feature until a patch is available.

Exploit

Fix

Information Disclosure

Weakness Enumeration

CWE-703CWE-200

Related Identifiers

GHSA-3CX6-J9J4-54MP

Affected Products

Decidim
Decidim-Core