dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-30960

CRITICAL · 9.4 CVSS v4.0 Published 2026-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
rssn is a scientific computing library for Rust, combining a high-performance symbolic computation engine with numerical methods support and physics simulations functionalities. The vulnerability exists in the JIT (Just-In-Time) compilation engine, which is fully exposed via the CFFI (Foreign Function Interface). Due to Improper Input Validation and External Control of Code Generation, an attacker can supply malicious parameters or instruction sequences through the CFFI layer. Since the library often operates with elevated privileges or within high-performance computing contexts, this allows for Arbitrary Code Execution (ACE) at the privilege level of the host process.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The rssn scientific computing library contains a critical vulnerability in its JIT compilation engine exposed via the CFFI layer. Due to improper input validation and external control of code generation, attackers can supply malicious parameters or instruction sequences through the foreign function interface to achieve arbitrary code execution at the host process's privilege level.

MitigationImplement rigorous input validation and sanitization at the CFFI boundary to validate all parameters and instruction sequences before JIT compilation. Consider sandboxing the JIT engine, adding compile-time authorization checks, or restricting the JIT exposure until secure-by-default controls are in place.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify rssn library installation
    Search for the rssn Rust library in your project's dependencies (e.g., Cargo.toml, package.json with rust bindings, or system libraries). Run 'grep -r "rssn"' in your codebase or check installed Rust crates with 'cargo tree -p rssn' if available.
    Affected if rssn library is present in your environment
  2. Determine rssn version
    Check the installed version of rssn by examining your lock file (Cargo.lock), or run 'cargo info rssn' or check the library's version attribute in your dependency tree.
    Affected if the installed version falls within any known affected version range and the library is in use
  3. Verify CFFI exposure
    Search your codebase and configuration for CFFI (Foreign Function Interface) bindings that expose rssn functions. Look for patterns like 'ffi', 'foreign_function', 'libffi', or direct Rust-to-Python/other-language bindings involving rssn.
    Affected if CFFI bindings are defined that expose rssn functions to external callers
  4. Confirm JIT engine accessibility
    Inspect the CFFI interface for functions related to JIT compilation, such as 'jit', 'compile', 'execute', or similar. Review exported symbols from any rssn shared library with 'nm librssn.so' or equivalent.
    Affected if JIT-related functions are exposed through the CFFI layer to untrusted callers
  5. Check external caller access
    Review network configurations, API endpoints, or plugin systems that allow external input to reach the rssn CFFI interface. Identify if the CFFI boundary crosses trust boundaries (e.g., web-facing, multi-tenant, or unsandboxed callers).
    Affected if untrusted or external callers can supply parameters to the CFFI-exposed JIT engine

Your environment is affected if rssn with an exposed CFFI interface is present and external or untrusted callers can supply parameters to the JIT compilation functions through that interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement rigorous input validation and sanitization at the CFFI boundary to validate all parameters and instruction sequences before JIT compilation. Consider sandboxing the JIT engine, adding compile-time authorization checks, or restricting the JIT exposure until secure-by-default controls are in place.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30960 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data