CVE-2026-126074

Not enough EPSS history yet.

Active Storage makes it simple to upload and reference files in cloud services and attach those files to Active Record objects. Prior to 8.1.4.1 and 8.0.5.2, ActiveStorage::Filename#base and #extension_with_delimiter, and therefore #extension, pass the stored filename unmodified to File.basename and File.extname, which raise ArgumentError when the name contains a NUL byte. Active Storage stores the client-supplied filename verbatim, so a user who is permitted to upload an attachment could persist such a filename on databases that accept NUL bytes in string columns, such as SQLite and MySQL/MariaDB. Each subsequent request that builds a variant or preview of the blob, opens it, or renders it as an Action Text attachment then raises, possibly resulting in a persistent DoS vulnerability for the pages that display the blob until it is purged or its filename is corrected. Applications that use PostgreSQL are not affected, because PostgreSQL rejects the row. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.

• github.comhttps://github.com/rails/rails/commit/60f22af88b71eae251f112d8c0237a08a8832692
• github.comhttps://github.com/rails/rails/commit/9b0d4bef2211a2c08cab2e0ea17fa1d0efd5d47a
• github.comhttps://github.com/rails/rails/releases/tag/v8.0.5.2
• github.comhttps://github.com/rails/rails/releases/tag/v8.1.4.1
• github.comhttps://github.com/rails/rails/security/advisories/GHSA-p2pm-g2h6-7j5j