ruby vulnerabilities — 6 matching vulnerabilities
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed — no installation and no source-code access required.
| Severity | Vulnerability | Package | Ecosystem | Disclosed | Fixed version |
|---|---|---|---|---|---|
| Medium | UNKNOWN READ Vulnerability in Ruby Package - OSV-2026-4 |
ruby
|
OSS-Fuzz | 04 Jan 2026 | No fix published |
| Medium | Heap-buffer-overflow in fill_lines in Ruby |
ruby
|
OSS-Fuzz | 17 Nov 2023 | f5c3cda7d6e9053ae5ed66e36d13e568595ff1ec |
| High | Use-after-poison in parser_yylex in ruby |
ruby
|
OSS-Fuzz | 02 Sep 2023 | No fix published |
| High | Use-after-poison in str_new_frozen_buffer in Ruby |
ruby
|
OSS-Fuzz | 17 Apr 2023 | 628e432739e1d2578d357420aa652a97eb8c2649 |
| High | Use-after-poison vulnerability in rb_gc_writebarrier in Ruby |
ruby
|
OSS-Fuzz | 09 Apr 2023 | No fix published |
| Medium | Use-after-poison vulnerability in Ruby |
ruby
|
OSS-Fuzz | 29 Oct 2022 | No fix published |
Questions
Searching the database
How do I search for a CVE or a package?
Type a CVE id, package name, ecosystem or keyword into the search field. Results include the severity, the affected package, the ecosystem, the disclosure date and the fixed version.
Can I filter by severity or by whether a fix exists?
Yes. The filters on the left narrow the list to critical, high, medium or low vulnerabilities, to a single ecosystem, and to vulnerabilities that have a fix available or none yet.
What does "No fix published" mean?
No patched version has been released for that vulnerability yet. The vulnerability page still shows the affected range and any workaround that can reduce exposure in the meantime.