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