← Back
GHSA-x26h-xmv8-gxf7
Vulnerability in stigmem-node (GHSA-x26h-xmv8-gxf7)
Summary
vulnerability in stigmem-node (GHSA-x26h-xmv8-gxf7). Risk of unauthorized operations or information disclosure. Exploitable via ``issue_tombstone``. Mitigation: upgrade to `0.9.0a12` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-x26h-xmv8-gxf7** has been found in stigmem-node.
Attackers can target a specific entry point like ``issue_tombstone`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade stigmem-node to **0.9.0a12** or later.
If unsure, ask your IT team or search "stigmem-node GHSA-x26h-xmv8-gxf7" on the vendor's site.
GHSA-x26h-xmv8-gxf7 (stigmem-node) — CWE-639 /
Attack surface: `issue_tombstone` / `_get_tombstone_filter` / `_tombstone_scope_cache` / `tenant_id`
Patched: `0.9.0a12` — apply immediately
Workaround: None other than upgrading to `0.9.0a12`.
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** (CWE-639) exists in stigmem-node. Attackers reach the vulnerable code path via ``issue_tombstone`` without authentication.
📍 Affected scope
stigmem-node — . Attack surface: `issue_tombstone` / `_get_tombstone_filter` / `_tombstone_scope_cache` / `tenant_id`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.9.0a12**.
🛡️ Workaround
Workaround: None other than upgrading to `0.9.0a12`.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'stigmem-node' .` 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 'stigmem-node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `stigmem-node` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
None other than upgrading to `0.9.0a12`.パッチが適用されるまでの応急処置として、None other than upgrading to `0.9.0a12`. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade stigmem-node to 0.9.0a12ステージング環境で 0.9.0a12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
stigmem-node
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.9.0a12"}]}]