← Back
CVE-2026-46690
medium
CVSS 5.8
Out-of-Bounds Read in unbounded-spsc (CVE-2026-46690)
Summary
vulnerability in unbounded-spsc (CVE-2026-46690). Risk of unauthorized operations or information disclosure. Exploitable via ``unsafe``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-46690** has been found in unbounded-spsc.
Attackers can target a specific entry point like ``unsafe`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "unbounded-spsc CVE-2026-46690" on the vendor's site.
CVE-2026-46690 (unbounded-spsc) — CWE-125 / CVSS v3 5.8
Attack vector: local / no user interaction
Attack surface: `unsafe` / `DISCONNECTED` / `producer` / `Sender`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**out-of-bounds read** (CWE-125) exists in unbounded-spsc. Attackers reach the vulnerable code path via ``unsafe`` without authentication.
📍 Affected scope
unbounded-spsc — . Attack surface: `unsafe` / `DISCONNECTED` / `producer` / `Sender`.
🔥 Severity
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'unbounded-spsc' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'unbounded-spsc' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `unbounded-spsc` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
unbounded-spsc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
crates.io
unbounded-spsc
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.2.0"}]}]