CVE-2026-126074

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.3 from GitHub Security Advisory (severity: MODERATE) published 2026-11-10. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-122910 (ENISA EUVD) · GHSA-p2pm-g2h6-7j5j (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.3
EG Score
4.3MEDIUMhigh confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 10, 2026

Last Modified

November 13, 2026

Advisory Details (5)

Auto-updated Nov 13, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

8.1.4.1

Patch available: rails/rails v8.1.4.1

https://github.com/rails/rails/releases/tag/v8.1.4.1
GitHub release Patch Available

8.0.5.2

Patch available: rails/rails v8.0.5.2

https://github.com/rails/rails/releases/tag/v8.0.5.2
GitHub commit

commit 9b0d4bef2211 (rails/rails)

Fix landed in rails/rails commit 9b0d4bef2211 — awaiting tagged release

https://github.com/rails/rails/commit/9b0d4bef2211a2c08cab2e0ea17fa1d0efd5d47a
GitHub commit

commit 60f22af88b71 (rails/rails)

Fix landed in rails/rails commit 60f22af88b71 — awaiting tagged release

https://github.com/rails/rails/commit/60f22af88b71eae251f112d8c0237a08a8832692
GitHub advisoryMentions a patch (unverified)

Possible DoS vulnerability in Active Storage filename handling · Advisory · rails/rails · GitHub

https://github.com/rails/rails/security/advisories/GHSA-p2pm-g2h6-7j5j

Vendor Advisories for CVE-2026-126074(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rubygemsactivestorage @ 8.1.4.1 (fixes >= 8.1.0.beta1, < 8.1.4.1)—ghsa
rubygemsactivestorage @ 8.0.5.2 (fixes < 8.0.5.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
activestorage0.1 ... 8.0.5.1 (177 versions)
  • 8.1.0.beta1 up to 8.1.4.1: fixed in 8.1.4.1
  • every version up to 8.0.5.2: fixed in 8.0.5.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 17:31 UTCEchelonGraph re-scored
  2. 2026-11-13 17:31 UTCGHSA enrichmentGHSA-p2pm-g2h6-7j5j · GitHub severity MODERATE · GitHub CVSS 4.3
  3. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-13 16:29 UTCEchelonGraph re-scored
  5. 2026-11-13 16:29 UTCGHSA enrichmentGHSA-p2pm-g2h6-7j5j · GitHub severity MODERATE · GitHub CVSS 4.3
  6. 2026-11-12 22:32 UTCEchelonGraph re-scored
  7. 2026-11-12 22:32 UTCGHSA enrichmentGHSA-p2pm-g2h6-7j5j · GitHub severity MODERATE · GitHub CVSS 4.3
  8. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-11-10 22:00 UTCENISA EUVD ID recordedEUVD-2026-122910 · Source: ENISA EUVD
  11. 2026-11-10 21:33 UTCEchelonGraph re-scored
  12. 2026-11-10 20:51 UTCEchelonGraph re-scoredFirst assessed: 4.3 MEDIUM
  13. 2026-11-10 20:50 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-126074?
CVE-2026-126074 is a medium-severity vulnerability; its CVE record was published on November 10, 2026. 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…
When was the CVE record for CVE-2026-126074 published?
The CVE record for CVE-2026-126074 was published on November 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 13, 2026; the record at its source may have been updated since.
Is CVE-2026-126074 actively exploited?
CVE-2026-126074 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-126074?
CVE-2026-126074 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-126074?
A fix for CVE-2026-126074 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-126074 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-126074

Explore →

Is Your Infrastructure Affected by CVE-2026-126074?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs