← Back
OSV-2026-1027
Vulnerability in tarantool (OSV-2026-1027)
Summary
vulnerability in tarantool (OSV-2026-1027). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `42d7de284ffb896006e74a51fbd0f62318b813ba` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **OSV-2026-1027** has been found in tarantool.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade tarantool to **42d7de284ffb896006e74a51fbd0f62318b813ba** or later.
If unsure, ask your IT team or search "tarantool OSV-2026-1027" on the vendor's site.
OSV-2026-1027 (tarantool) —
Patched: `42d7de284ffb896006e74a51fbd0f62318b813ba` — 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 tarantool.
📍 Affected scope
tarantool — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **42d7de284ffb896006e74a51fbd0f62318b813ba**.
🛡️ 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 'tarantool' .` 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 'tarantool' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `tarantool` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade tarantool to 42d7de284ffb896006e74a51fbd0f62318b813baステージング環境で 42d7de284ffb896006e74a51fbd0f62318b813ba に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
OSS-Fuzz
tarantool
[{"repo":"https:\/\/github.com\/tarantool\/tarantool","type":"GIT","events":[{"introduced":"c679fad72328070e9d94426077b8cc45c390e313"},{"fixed":"42d7de284ffb896006e74a51fbd0f62318b813ba"}]}]