{"id":"CVE-2018-10199","url":"https://www.cyber-defence.io/tools/cve/CVE-2018-10199","generatedAt":"2026-10-29T01:41:27.818Z","title":"In versions of mruby up to and including 1.4.0, a use-after-free vulnerability exists in src/io.c::File#initilialize_copy().","description":"In versions of mruby up to and including 1.4.0, a use-after-free vulnerability exists in src/io.c::File#initilialize_copy(). An attacker that can cause Ruby code to be run can possibly use this to execute arbitrary code.","published":"2018-04-18T15:29:00.000Z","lastModified":"2026-06-17T01:33:40.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.0","score":9.8,"severity":"CRITICAL","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"},"cwe":["CWE-416"],"affected":["mruby/mruby"],"epss":{"score":0.02264,"percentile":0.82915,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (2.26%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://github.com/mruby/mruby/commit/b51b21fc63c9805862322551387d9036f2b63433","tags":["Patch"],"source":"cve@mitre.org"},{"url":"https://github.com/mruby/mruby/issues/4001","tags":["Third Party Advisory"],"source":"cve@mitre.org"},{"url":"https://github.com/mruby/mruby/commit/b51b21fc63c9805862322551387d9036f2b63433","tags":["Patch"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://github.com/mruby/mruby/issues/4001","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2018-10199","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}