RisingWave CVE-2026-112262

Requires a valid, authenticated RisingWave SQL account that holds CREATE privilege on at least one schema (PR:L); there is no unauthenticated path. In affected versions (<3.1.0) the local filesystem connectors (posix_fs source and fs sink) were permitted by default, so no special victim-side configuration is needed - the attacker simply sets posix_fs.root or fs.path to any directory. Files are read/written with the privileges of the RisingWave server process (described as root), enabling credential/key theft or arbitrary file creation. Limiting factors: the attacker must already possess low-privilege DB credentials with schema CREATE; no user interaction is required. The 3.1.0 fix neutralizes default exploitation by gating these connectors behind frontend.unsafe_enable_local_fs_connector, which defaults to false in release builds.

The vendor/NVD CVSS 4.0 score of 7.1 (High) is driven by AV:N/AC:L/AT:N/PR:L/UI:N - meaning any authenticated low-privilege SQL user holding schema CREATE can trigger this remotely, with no special complexity and no user interaction. The declared impact (VC:H/VI:L) captures high-confidentiality disclosure of credentials and keys but, in my view, understates the integrity impact: the description states files can be written 'as root,' which is a severe integrity (and potential host-compromise) primitive that I assess higher than VI:L. Exploitation status: no public exploit identified at time of analysis - no EPSS score, no CISA KEV listing, and no POC were provided (the GitHub 'source code evidence' is the vendor patch diff, not exploit code), so there is no indication of active or widespread exploitation. The key limiting factor is the PR:L prerequisite: this is not an unauthenticated internet-facing bug but a post-authentication authorization gap (CWE-862), so realistic risk is highest in multi-tenant deployments or against insiders/compromised low-privilege accounts rather than mass exploitation. The patch's design - gating these connectors behind a config flag disabled by default in release builds - confirms the root cause was that local filesystem connectors were permitted by default.

An attacker with a low-privileged RisingWave SQL account that holds CREATE privilege on a schema issues CREATE SOURCE with connector 'posix_fs' and posix_fs.root pointing at a sensitive directory (e.g., /root/.ssh or /etc) to read credentials and keys, or CREATE SINK with connector 'fs' and fs.path set to an arbitrary path to write files as the root process user. No public exploit code was identified, though the fixing patch (PR #25971) is public and reveals the exact connectors and parameters involved.