Vulnerability Database · OSS-Fuzz · ruby · Version

ruby v3_3_6

v3_3_6 is affected by 4 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 2 Medium 2 Low 0 Unrated 0

Database updated 23/Oct/2026

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.

01 Vulnerabilities affecting this version

ruby v3_3_6 vulnerabilities

4 vulnerabilities cover ruby v3_3_6. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
UNKNOWN READ Vulnerability in Ruby Package - OSV-2026-4 N/A medium No fix published 04 Jan 2026
Use-after-poison in parser_yylex in ruby N/A high No fix published 02 Sep 2023
Use-after-poison vulnerability in rb_gc_writebarrier in Ruby N/A high No fix published 09 Apr 2023
Use-after-poison vulnerability in Ruby N/A medium No fix published 29 Oct 2022

Looking for another version, or everything Vulert holds for ruby?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About ruby v3_3_6

Is ruby v3_3_6 vulnerable?

Yes. 4 vulnerabilities in the Vulert database cover ruby v3_3_6: 0 critical, 2 high, 2 medium and 0 low. Each entry above names the fixed version to move to.

How do I monitor ruby for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ruby version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.