← Back
CVE-2026-41147
high
CVSS 8.7
Cross-Site Scripting (XSS) in nukeviet/nukeviet (CVE-2026-41147)
Summary
cross-site scripting in nukeviet/nukeviet (CVE-2026-41147). Confidential information can be exposed externally. Exploitable via ``srcdoc``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41147** has been found in nukeviet/nukeviet.
Attackers can target a specific entry point like ``srcdoc`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "nukeviet/nukeviet CVE-2026-41147" on the vendor's site.
CVE-2026-41147 (nukeviet/nukeviet) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: `srcdoc` / `onerror` / `onload` / `HttpOnly`
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
**Cross-site scripting (XSS)** (CWE-79) exists in nukeviet/nukeviet. Attackers reach the vulnerable code path via ``srcdoc`` without authentication.
📍 Affected scope
nukeviet/nukeviet — . Attack surface: `srcdoc` / `onerror` / `onload` / `HttpOnly`.
🔥 Severity
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 'nukeviet/nukeviet' .` 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 'nukeviet/nukeviet' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `nukeviet/nukeviet` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
nukeviet/nukeviet
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Packagist
nukeviet/nukeviet
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"4.4.01"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41147
- package https://github.com/nukeviet/nukeviet
- web https://github.com/nukeviet/nukeviet/security/advisories/GHSA-64rr-pp78-62ww
- web https://github.com/nukeviet/nukeviet/commit/2a0860fbe22e2f6a3b90f802bf80b25e18699611
- web https://github.com/nukeviet/nukeviet/releases/tag/4.5.08
- web https://github.com/advisories/GHSA-64rr-pp78-62ww