NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
CRITICAL severity

CVE-2022-28481 — csv-safe

CRITICALFix: zvory/csv-safe#8

CVE-2022-28481 is a critical-severity (CVSS 9.8) CWE-1236 vulnerability in csv-safe. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for csv-safe — see the affected versions and patch details below.

CSV-Safe improperly filters special characters potentially leading to CSV injection

Also known asGHSA-f55g-x8qq-2569
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk
0.00%0.75%1.50%2.26%0.4%1.8%May 26Aug 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
💎csv-safe

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

CSV-Safe gem < 3.0.0 doesn't filter out special characters which could trigger CSV Injection.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemscsv-safeall versions3.0.0bundle update csv-safe --conservative

Affected Products

1 product · 1 configurations
Application
csv-safecsv-safe_project
< 3.0.0
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

CSV-Safe gem < 3.0.0 doesn't filter out special characters which could t…

github.comNVDMay 2022

Report on github.com

github.comNVDMay 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for csv-safe, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update csv-safe to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28481 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

CSV-Safe gem < 3.0.0 doesn't filter out special characters which could trigger CSV Injection.
O3 Security · Impact-Aware SCA

Is CVE-2022-28481 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-28481: csv-safe — Fixed in 3.0.0