Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-p2pm-g2h6-7j5j | Active Storage: Possible DoS vulnerability in Active Storage filename handling |
Tue, 10 Nov 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Active Storage: Possible DoS vulnerability in Active Storage filename handling | |
| Weaknesses | CWE-248 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-10T20:48:25.207Z
Reserved: 2026-11-10T17:07:43.284Z
Link: CVE-2026-126074
No data.
Status : Received
Published: 2026-11-10T21:19:25.720
Modified: 2026-11-10T21:19:25.720
Link: CVE-2026-126074
No data.
OpenCVE Enrichment
No data.
Github GHSA