CVE-2026-44837: ViewComponent view_component · Partial String Comparison
Affects ViewComponent view_componentSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 4.9.0 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.9.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 May 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 29 Oct 2026.
What to do
Upgrade view_component and view_component/view_component to 4.9.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ViewComponentview_component | Affected
| Fixed in
|
RubyGemsview_component/view_componentpkg:gem/view_component/view_componentOther threats | Affected
| 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 view_component version 4.9.0. Users of affected versions (>= 3.0.0 and < 4.9.0) should upgrade to version 4.9.0 or later to remediate this issue. Patch status is not explicitly stated beyond the fix in 4.9.0, so upgrading to this version is the recommended remediation.
Description
view_component is a framework for building reusable, testable, and encapsulated view components in Ruby on Rails. From 3.0.0 to 4.9.0, the system test entrypoint canonicalizes a user-controlled file path with File.realpath, then checks whether the resolved path starts with the temp directory path. This is not a safe containment check because sibling directories can share the same string prefix. This vulnerability is fixed in 4.9.0.