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