← Back
CVE-2026-47253
Path Traversal in github.com/julien040/anyquery (CVE-2026-47253)
Summary
path traversal in github.com/julien040/anyquery (CVE-2026-47253). Data can be tampered with by attackers. Exploitable via `GET /list-tables`. Mitigation: upgrade to `0.4.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47253** has been found in github.com/julien040/anyquery.
Attackers can target a specific entry point like `GET /list-tables` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade github.com/julien040/anyquery to **0.4.5** or later.
If unsure, ask your IT team or search "github.com/julien040/anyquery CVE-2026-47253" on the vendor's site.
CVE-2026-47253 (github.com/julien040/anyquery) — CWE-22 /
Attack vector: remote (network-reachable)
Attack surface: GET /list-tables / POST /execute-query... / POST /execute-query / `clear_plugin_cache`
Patched: `0.4.5` — 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
**Path traversal** (CWE-22) exists in github.com/julien040/anyquery. Attackers reach the vulnerable code path via `GET /list-tables` without authentication.
📍 Affected scope
github.com/julien040/anyquery — . Attack surface: GET /list-tables / POST /execute-query... / POST /execute-query / `clear_plugin_cache`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **0.4.5**.
🛡️ 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 `GET /list-tables` requests with malformed payloads or SQL meta-characters. Run `grep -r 'github.com/julien040/anyquery' .` 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/julien040/anyquery` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /list-tables' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /list-tables` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade github.com/julien040/anyquery to 0.4.5ステージング環境で 0.4.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /list-tables on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/julien040/anyquery
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.4.5"}]}]