SurrealKV out-of-bounds read in InternalKeyRef decoder
Affects SurrealKV before 1.1.0 when a key shorter than 16 bytes reaches InternalKeyRef::from_encoded, or a crafted or corrupted SSTable yields such a key during decoding. Fixed in 1.1.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.1.0
- Who is exposed
- Specific setups only
Summary
Written by a model
SurrealKV before 1.1.0 contains an out-of-bounds read vulnerability in the safe InternalKeyRef::from_encoded constructor, which only checks key length with a debug-only assertion. Callers passing keys shorter than 16 bytes, or crafted or corrupted SSTable blocks, trigger unchecked length underflow in timestamp(), seq_num() and trailer(), reading heap bytes before the allocation or panicking.
Who should check
Rust teams depending on surrealkv before 1.2.0 from crates.io, including SurrealDB builds with the kv-surrealkv feature.
“surrealkv is a published crate, so any downstream Rust code can trigger it”
What to do
Check whether your setup matches what the bug needs.
Caller passes a slice shorter than 16 bytes to InternalKeyRef::from_encoded. A crafted or corrupted SSTable block yields a key shorter than 16 bytes during decoding.Upgrade to a fixed version: 1.1.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134303 (SurrealKV before 1.1.0 Out-of-Bounds Read via InternalKeyRef Decoder), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134303 (entry last updated 2026-11-21):
Affected:
- crates.io package surrealkv: fixed in 1.1.0
Fixed versions: 1.1.0.
Conditions (all must be true for the bug to be hit):
- Caller passes a slice shorter than 16 bytes to InternalKeyRef::from_encoded. (source: https://www.vulncheck.com/advisories/surrealkv-before-1.1.0-out-of-bounds-read-via-internalkeyref-decoder)
- A crafted or corrupted SSTable block yields a key shorter than 16 bytes during decoding. (source: https://github.com/surrealdb/surrealdb/security/advisories/GHSA-9fm9-c4h4-8g93)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, no user action.
CISA KEV: CVE-2026-134303 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134303 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/surrealdb/surrealdb/security/advisories/GHSA-9fm9-c4h4-8g93
- https://github.com/surrealdb/surrealdb/commit/914c3ce374bb5d75b10079385a3efb31a9d96e63
- https://www.vulncheck.com/advisories/surrealkv-before-1.1.0-out-of-bounds-read-via-internalkeyref-decoder
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134303
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134303"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach10/20Affects crates.io packages
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 33 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · surrealdb/surrealdb · Advisory GHSA-9fm9-c4h4-8g93 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134303 |
| Record | NVD · CVE-2026-134303 |
| Other links 2 | |
| Patch | GitHub · surrealdb/surrealdb · Commit 914c3ce3 |
| Link | vulncheck.com · advisories/surrealkv-before-1.1.0-out-of-bounds-read-via-internalkeyref-decoder |
Questions about CVE-2026-134303
Is CVE-2026-134303 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Decoding a key shorter than 16 bytes through InternalKeyRef can read heap bytes before the allocation in release builds, or panic in debug builds.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134303?
surrealkv (crates.io): before 1.1.0.
Source: cve.now feed data
Am I affected, and how do I check?
SurrealKV versions before 1.1.0 are in the affected range. The exposure requires either a caller passing a slice shorter than 16 bytes to InternalKeyRef::from_encoded, or a crafted or corrupted SSTable block that yields such a key during decoding. Check the SurrealKV version in the project's dependency lockfile to see whether it falls before 1.1.0.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134303?
Upgrade SurrealKV to 1.1.0 or later, the fixed version.
Source: vulncheck.com, github.com
Related
- CVE-2026-134292SurrealDB 1.0.0 before 4.0.0 Function Capability Bypass via JavaScript Built-in Bridge
- CVE-2026-134293SurrealDB 3.1.0 before 4.0.0 SQL Injection via MCP Tool Identifier Escaped Backticks
- CVE-2026-134291SurrealDB 3.0.0 before 4.0.0 Path Traversal via Filesystem Bucket Symlinks
- CVE-2026-134294SurrealDB 3.0.0 before 4.0.0 Path Traversal via Windows Backslashes in Bucket Keys
- CVE-2026-134295SurrealDB 3.0.0 before 4.0.0 Path Traversal in Direct Filesystem Buckets
- CVE-2026-134299SurrealDB 3.0.4 before 4.0.0 Memory Exhaustion via GraphQL WebSocket Upgrade
No corrections so far. Something wrong on this page? Report an error.