Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-47731 critical CVSS 9.1

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.

Original description

The description as published by the source.

1. Summary

The Binary Stream Capture (BSC) component exposes an unauthenticated HTTP API for dynamically creating packet capture “handlers.” Because the code blindly trusts path‑related form fields, a remote client can:

  • Bypass the configured log root and direct BSC to log to arbitrary filesystem paths (path traversal / directory escape), and
  • Append attacker‑controlled data to those files, using the privileges of theait-bsc process.

There are two ways for a remote attacker to trigger this:

  1. If the attacker has access to the network where ait-bsc is deployed (a reason for that could be that the ports are publicly accessible), the payloads can be directly sent to the server to trigger the arbitrary file append. This type of attack is demonstrated in python_poc.py.
  2. Even if the attacker does not have direct access to the network because the software is running in a local network, it is possible to exploit this if a bad actor in that network opens an attacker-controlled website (which might be a website created by an attacker, or a third-party website compromised by the attacker). The browser javascript can automatically send the requests necessary to exploit this into the local network. This is even possible if the server is only accessible on localhost. This type of attack is demonstrated by attacker_tcp.py and test1.html (first launch the attacker TCP server, then start a webserver to host test1.html, for example using `python3 -m http.se…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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: 9.1/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 / CVSS v3 9.1
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

Check the vendor advisory for the affected versions of ait-core. Attack surface: python_poc.py / localhost / attacker_tcp.py / test1.html.

🔥 Severity

Severity: Critical (CVSS 9.1/10). 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'ait-core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で ait-core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade ait-core to 2.6.1

    ステージング環境で 2.6.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"},{"introduced":"3.1.0"},{"fixed":"3.1.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details