← Back
CVE-2026-47731
Path Traversal in ait-core (CVE-2026-47731)
Summary
path traversal in ait-core (CVE-2026-47731). Data can be tampered with by attackers. Exploitable via ``python_poc.py``. Mitigation: upgrade to `2.6.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47731** has been found in ait-core.
Attackers can target a specific entry point like ``python_poc.py`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade ait-core to **2.6.1** or later.
If unsure, ask your IT team or search "ait-core CVE-2026-47731" on the vendor's site.
CVE-2026-47731 (ait-core) — CWE-22 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `python_poc.py` / `localhost` / `attacker_tcp.py` / `test1.html`
Patched: `2.6.1` — 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 ait-core. Attackers reach the vulnerable code path via ``python_poc.py`` without authentication.
📍 Affected scope
ait-core — . Attack surface: `python_poc.py` / `localhost` / `attacker_tcp.py` / `test1.html`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **2.6.1**.
🛡️ 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 'ait-core' .` 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 'ait-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ait-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade ait-core to 2.6.1ステージング環境で 2.6.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
ait-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.1"}]}]
PyPI
ait-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.1"}]}]
References
- package https://github.com/NASA-AMMOS/AIT-Core
- web https://github.com/NASA-AMMOS/AIT-Core/security/advisories/GHSA-p462-prxw-mjx4
- web https://github.com/NASA-AMMOS/AIT-Core/releases/tag/2.6.1
- web https://github.com/NASA-AMMOS/AIT-Core/releases/tag/3.1.1
- web https://github.com/advisories/GHSA-p462-prxw-mjx4