← Back
RUSTSEC-2026-0129
Vulnerability in dahl-salso (RUSTSEC-2026-0129)
Summary
vulnerability in dahl-salso (RUSTSEC-2026-0129). Risk of unauthorized operations or information disclosure. Exploitable via ``from_i32_column_major_order``. Mitigation: upgrade to `0.6.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **RUSTSEC-2026-0129** has been found in dahl-salso.
Attackers can target a specific entry point like ``from_i32_column_major_order`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade dahl-salso to **0.6.8** or later.
If unsure, ask your IT team or search "dahl-salso RUSTSEC-2026-0129" on the vendor's site.
RUSTSEC-2026-0129 (dahl-salso) —
Attack surface: `from_i32_column_major_order` / `labels` / `n_items` / `n_clusterings`
Patched: `0.6.8` — apply immediately
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
**A vulnerability** (unclassified) exists in dahl-salso. Attackers reach the vulnerable code path via ``from_i32_column_major_order`` without authentication.
📍 Affected scope
dahl-salso — . Attack surface: `from_i32_column_major_order` / `labels` / `n_items` / `n_clusterings`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.6.8**.
🛡️ 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 'dahl-salso' .` 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 'dahl-salso' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `dahl-salso` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade dahl-salso to 0.6.8ステージング環境で 0.6.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
crates.io
dahl-salso
[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.6.8"}]}]