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