Is stringio 0.0 vulnerable?

RubyGems · 2 releases from 0.0.1 to 0.0.2 · latest stringio is 3.2.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. stringio 0.0.2, the last 0.0 release, is affected by 1 known security advisory (1 critical), including CVE-2024-27280. Upgrade to 3.0.1.1 or later to fix all of them.

Upgrade with:bundle update --conservative stringio # Gemfile: '>= 3.0.1.1'

Is your project on an affected stringio?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting stringio 0.0.2

  • CriticalCVE-2024-27280GHSA-v5h6-c2hv-hv3r25 Mar 2024

    StringIO buffer overread vulnerability

    Affected
    <3.0.1.1
    Fixed in
    3.0.1.1

Every stringio 0.0.x release

Affected: 0.0.1 to 0.0.2. Latest stringio: 3.2.0.

VersionKnown advisories
stringio 0.0.2CVE-2024-27280
stringio 0.0.1CVE-2024-27280

Which of your client projects are still on stringio 0.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact stringio version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other stringio versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.