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

CVE-2022-23066 — solana_rbpf

CRITICALFix: solana-labs/rbpf@e61e045

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

Solana rBPF - Incorrect Calculation in sdiv instruction

Also known asGHSA-9qmm-4mfr-r3wj
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk
0.45%1.30%2.16%3.02%0.9%2.5%May 26Sep 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
🦀solana_rbpf

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

Description

In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to transfer tokens or not. The vulnerability affects both integrity and may cause serious availability problems.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iosolana_rbpf≥ 0.2.26&&< 0.2.280.2.28cargo update -p solana_rbpf --precise 0.2.28

Affected Products

1 product · 2 configurations
Application
rbpfsolana
2 versions
0.2.260.2.27
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.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update solana_rbpf to 0.2.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23066 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

In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to transfer tokens or not. The vulnerability affects both integrity and may cause serious availability problems.
O3 Security · Impact-Aware SCA

Is CVE-2022-23066 in your dependencies?

Find it across crates.io, including transitive dependencies.

CVE-2022-23066: solana_rbpf — Fixed in 0.2.28