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