# CVE-2026-112262: RisingWave before 3.1.0 Missing Authorization via posix_fs and fs Connectors

> Low-privileged users can read or write arbitrary server files via posix_fs and fs connectors, exposing credentials and allowing file modification.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-55ch-h383-9r92

## What is CVE-2026-112262?

CVE-2026-112262 is a high-severity missing authorization vulnerability in risingwavelabs risingwave, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RisingWave before 3.1.0 contains a missing authorization vulnerability that allows low-privileged SQL users to read and write arbitrary server files by creating posix_fs sources and fs sinks. Attackers holding schema CREATE privilege can set posix_fs.root or fs.path to any directory to read credentials and keys or write files as root.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-112262?


## How do I fix CVE-2026-112262?

No fix has been published for CVE-2026-112262 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112262 being exploited?

There is no known exploitation of CVE-2026-112262 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112262 and fix it if it is affected.

What it is: CVE-2026-112262 is a high-severity missing authorization vulnerability in risingwavelabs risingwave, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112262 in the wild and no public exploit code.

Affected product: risingwavelabs risingwave. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112262/ (Markdown: https://insights.sbomify.com/CVE-2026-112262/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112262
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112262
- OSV: https://osv.dev/vulnerability/CVE-2026-112262

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112262/
Summaries are generated and may contain mistakes; the official description above is the record.