Directory traversal vulnerability in Action View in Ruby on Rails before 3.2.22.1, 4.0.x and 4.1.x before 4.1.14.1, 4.2.x before 4.2.5.1, and 5.x before 5.0.0.beta1.1 allows remote attackers to read arbitrary files by leveraging an application's unrestricted use of the render method and providing a .. (dot dot) in a pathname.
CVE-2016-0752
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 9.0(high)
- EPSS
- 99.9%
- KEV
- ⚠ Exploited
Published
February 16, 2016
Last Modified
April 22, 2026
Advisory Details (5)
Auto-updated May 20, 2026oss-security - [CVE-2016-0752] Possible Information Leak Vulnerability in Action View
http://www.openwall.com/lists/oss-security/2016/01/25/13Vendor Advisories for CVE-2016-0752(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | ror40-rubygem-activesupport-1:4.0.2-4.el7 | 2016-03-15 | redhat |
| redhat | ruby193-rubygem-activesupport-1:3.2.8-6.el7 | 2016-03-15 | redhat |
| redhat | rh-ror41-rubygem-activesupport-1:4.1.5-3.el7 | 2016-02-24 | redhat |
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
(2 across 1 ecosystem)
RubyGems(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| actionpack | 0.9.0 ... 3.2.9.rc3 (176 versions) | 3.2.22.1 | — |
| actionview | 4.2.0 ... 4.2.5.rc2 (14 versions) | 4.2.5.1 | — |
Data Freshness Timeline
(refreshed 41× in last 7d / 185× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 352 total refreshes for this CVE.
- 2026-07-22 14:12 UTCVendor advisory
- 2026-07-22 09:50 UTCVendor advisory
- 2026-07-22 05:31 UTCVendor advisory
- 2026-07-22 01:10 UTCVendor advisory
- 2026-07-21 17:30 UTCVendor advisory
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:10 UTCVendor advisory
- 2026-07-21 08:51 UTCVendor advisory
- 2026-07-21 04:31 UTCVendor advisory
- 2026-07-21 00:11 UTCVendor advisory
- 2026-07-20 19:51 UTCVendor advisory
- 2026-07-20 15:32 UTCVendor advisory
- 2026-07-20 11:12 UTCVendor advisory
- 2026-07-20 06:52 UTCVendor advisory
- 2026-07-20 02:19 UTCVendor advisory
- 2026-07-19 21:59 UTCVendor advisory
- 2026-07-19 17:40 UTCVendor advisory
- 2026-07-19 13:20 UTCVendor advisory
- 2026-07-19 09:01 UTCVendor advisory
- 2026-07-19 04:41 UTCVendor advisory
- 2026-07-19 00:22 UTCVendor advisory
- 2026-07-18 20:03 UTCVendor advisory
- 2026-07-18 15:42 UTCVendor advisory
- 2026-07-18 11:22 UTCVendor advisory
- 2026-07-18 07:03 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-18 02:44 UTCVendor advisory
- 2026-07-17 22:25 UTCVendor advisory
- 2026-07-17 18:05 UTCVendor advisory
- 2026-07-17 13:45 UTCVendor advisory
- 2026-07-17 09:26 UTCEG score recompute
- 2026-07-17 09:26 UTCVendor advisory
- 2026-07-17 05:06 UTCVendor advisory
- 2026-07-17 00:47 UTCVendor advisory
- 2026-07-16 20:27 UTCVendor advisory
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 16:08 UTCVendor advisory
- 2026-07-16 11:48 UTCVendor advisory
- 2026-07-16 07:28 UTCVendor advisory
- 2026-07-16 03:08 UTCVendor advisory
- 2026-07-15 22:48 UTCVendor advisory
- 2026-07-15 18:28 UTCVendor advisory
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 14:07 UTCVendor advisory
- 2026-07-15 09:48 UTCVendor advisory
- 2026-07-15 05:29 UTCVendor advisory
- 2026-07-15 01:08 UTCVendor advisory
- 2026-07-14 20:48 UTCVendor advisory
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 16:28 UTCVendor advisory
- 2026-07-14 12:09 UTCVendor advisory
- 2026-07-14 07:50 UTCVendor advisory
- 2026-07-14 03:29 UTCVendor advisory
- 2026-07-13 23:10 UTCVendor advisory
- 2026-07-13 18:51 UTCVendor advisory
- 2026-07-13 17:07 UTCCISA KEV update
- 2026-07-13 14:31 UTCVendor advisory
- 2026-07-13 10:11 UTCVendor advisory
- 2026-07-13 05:51 UTCVendor advisory
- 2026-07-13 01:31 UTCVendor advisory
- 2026-07-12 21:12 UTCVendor advisory
- 2026-07-12 16:52 UTCVendor advisory
- 2026-07-12 12:32 UTCVendor advisory
- 2026-07-12 08:13 UTCVendor advisory
- 2026-07-12 05:42 UTCEPSS rescore
- 2026-07-12 03:53 UTCVendor advisory
- 2026-07-11 23:34 UTCVendor advisory
- 2026-07-11 19:14 UTCVendor advisory
- 2026-07-11 14:54 UTCVendor advisory
- 2026-07-11 10:35 UTCVendor advisory
- 2026-07-11 06:14 UTCVendor advisory
- 2026-07-11 01:55 UTCVendor advisory
- 2026-07-10 21:33 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
- 2026-07-10 17:14 UTCVendor advisory
- 2026-07-10 12:53 UTCVendor advisory
- 2026-07-10 08:33 UTCVendor advisory
- 2026-07-10 04:12 UTCVendor advisory
- 2026-07-09 23:50 UTCVendor advisory
- 2026-07-09 19:30 UTCVendor advisory
- 2026-07-09 15:11 UTCVendor advisory
- 2026-07-09 10:50 UTCVendor advisory
- 2026-07-09 06:27 UTCVendor advisory
- 2026-07-09 02:08 UTCVendor advisory
- 2026-07-08 21:47 UTCVendor advisory
- 2026-07-08 17:28 UTCVendor advisory
- 2026-07-08 13:08 UTCVendor advisory
- 2026-07-08 08:49 UTCVendor advisory
- 2026-07-08 04:30 UTCVendor advisory
- 2026-07-08 00:11 UTCVendor advisory
- 2026-07-07 19:51 UTCVendor advisory
- 2026-07-07 19:01 UTCCISA KEV update
- 2026-07-07 17:16 UTCCISA KEV update
- 2026-07-07 15:30 UTCVendor advisory
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-07 11:10 UTCVendor advisory
- 2026-07-07 06:50 UTCVendor advisory
- 2026-07-07 02:29 UTCVendor advisory
- 2026-07-06 22:08 UTCVendor advisory
Publicly available exploits
(3 references)Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-40561✓ verifiedFirst seen Oct 17, 2016
Ruby on Rails - Dynamic Render File Upload / Remote Code Execution (Metasploit)
Open source ↗ - Metasploitexploit/multi/http/rails_dynamic_render_code_exec✓ verifiedFirst seen Oct 16, 2016
Ruby on Rails Dynamic Render File Upload Remote Code Execution
Open source ↗ - Open source ↗GitHub PoCforced-request/rails-rce-cve-2016-0752First seen Jan 26, 2016
Related CVEs(same vendor)
Frequently asked(6)
What is CVE-2016-0752?
When was CVE-2016-0752 disclosed?
Is CVE-2016-0752 actively exploited?
What is the CVSS score of CVE-2016-0752?
Which products are affected by CVE-2016-0752?
How do I remediate CVE-2016-0752?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-0752
Is Your Infrastructure Affected by CVE-2016-0752?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.