HailBytes ASM Reliability Fixes: Exposure Graph, Attack Path & Asset Tables

The exposure graph and attack-path visualization are two of the views HailBytes ASM customers put in front of stakeholders most often — they're how you show an attack surface, not just list it. So when a front-end bundle initialization-ordering bug caused them to fail to load on some deployments, the impact was outsized: the product looked broken at exactly the moment it was meant to impress. A May 2026 patch fixes the root cause and adds diagnostics so this class of failure is visible instead of silent.

What was failing

Three customer-facing views had silent failure modes:

• Exposure graph — intermittently showed a "Graph library failed to load" alert because the Cytoscape.js window bridge initialized too late in the bundle.
• Attack-path visualization — the directed attack-path graph failed to render for the same bundle-ordering reason.
• Target asset tables — the per-target DataTable could hang on "Processing…" indefinitely because the AJAX data source had no error callback, so a failed request never surfaced.

What changed

The fix hardens how vendor globals are installed so the graph libraries are guaranteed to be available before the views that depend on them initialize — eliminating the ordering race for the exposure graph and attack-path views. The asset tables now have an explicit error callback on their data source, so a failed load shows an actionable error instead of an endless spinner. Added diagnostics make any future graph or table load failure report why it failed rather than failing quietly.

Do you need to do anything?

No. The fix ships in marketplace images published from late May 2026 onward; there's no configuration change. If you ever saw a graph view fail to load or an asset table stick on "Processing…", pulling the latest image resolves it.