VulnerabilityPublished 12 Nov 2026Updated 13 Nov 2026

CVE-2026-126085: Rails · Active Storage makes it simple to upload and reference files in cloud services and attach

Affects railsSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2020-8162

Authoritative record:CVE-2026-126085· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 8.1.4.1 : update rails when convenient.

Data as of 13 Nov 2026, 22:23 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	5.3

Patch: Available – fixed in 8.1.4.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10rails`pkg:deb/ubuntu/rails?arch=source&distro=stonking`Other threats	Affected =2:7.2.3+dfsg-2 =2:7.2.3.2+dfsg-2	Fixed in–
Ubuntu 26.04 LTSrails`pkg:deb/ubuntu/rails?arch=source&distro=resolute`Other threats	Affected =2:7.2.2.1+dfsg-7 =2:7.2.2.2+dfsg-2 =2:7.2.3+dfsg-2	Fixed in–
Ubuntu 24.04 LTSrails`pkg:deb/ubuntu/rails?arch=source&distro=noble`Other threats	Affected =2:6.1.7.3+dfsg-2build1 =2:6.1.7.3+dfsg-3	Fixed in–
Ubuntu Pro 22.04 LTSrails`pkg:deb/ubuntu/rails?arch=source&distro=esm-apps/jammy`Other threats	Affected =2:6.0.3.7+dfsg-2 =2:6.1.4.1+dfsg-8ubuntu2 =2:6.1.4.1+dfsg-8ubuntu2+esm1	Fixed in–
Ubuntu Pro 20.04 LTSrails`pkg:deb/ubuntu/rails?arch=source&distro=esm-apps/focal`Other threats	Affected =2:5.2.2.1+dfsg-1ubuntu1 =2:5.2.3+dfsg-3 =2:5.2.3+dfsg-3ubuntu0.1~esm1	Fixed in–
Ubuntu Pro 18.04 LTSrails`pkg:deb/ubuntu/rails?arch=source&distro=esm-apps/bionic`Other threats	Affected 2:4.2.9-2 – 2:4.2.10-0ubuntu4+esm2 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Rails versions 8.1.4.1 and 8.0.5.2. Applications using Active Storage with Google Cloud Storage for direct uploads should upgrade to at least these versions to remediate the issue. No additional mitigations are indicated by the vendor advisory.

Description

A vulnerability in Rails Active Storage prior to versions 8.1.4.1 and 8.0.5.2 allows direct-upload clients using Google Cloud Storage to upload files larger than the declared content length. This occurs because the signed direct-upload URL does not enforce the declared content length, potentially bypassing application file size validations and quotas.

Impact

An attacker or client uploading files directly to Google Cloud Storage via Active Storage can upload files larger than the declared size, potentially bypassing file size restrictions and quotas enforced by the application. This could lead to resource exhaustion or unintended storage usage. The vulnerability does not impact confidentiality or availability directly but affects integrity by allowing larger-than-intended files to be stored.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 22:23 UTC

Technical details

References

Community reviews

Related threats