Fluid Attacks incident

Blank screen when accessing SCA findings

Notice Resolved View vendor source →

Fluid Attacks experienced a notice incident on October 6, 2025 affecting Platform, lasting 1h 10m. The incident has been resolved; the full update timeline is below.

Started
Oct 06, 2025, 02:11 PM UTC
Resolved
Oct 06, 2025, 03:22 PM UTC
Duration
1h 10m
Detected by Pingoru
Oct 06, 2025, 02:11 PM UTC

Affected components

Platform

Update timeline

  1. identified Oct 06, 2025, 02:11 PM UTC

    It has been observed that when accessing SCA findings, the platform displays a blank screen.

  2. resolved Oct 06, 2025, 03:22 PM UTC

    The incident has been resolved, and findings now load and display correctly.

  3. postmortem Oct 07, 2025, 04:16 PM UTC

    **Impact** At least three users experienced a blank screen issue when accessing certain vulnerabilities. The issue started on UTC-5 25-10-03 23:52 and was reactively discovered 1.8 days \(TTD\) later by a customer who reported through our help desk [\[1\]](https://help.fluidattacks.com/agent/fluid4ttacks/fluid-attacks/tickets/details/944043000049381865) that it was not possible to access some Weaknesses. These weaknesses were linked to vulnerabilities reported under SCA, and every organization or group with weaknesses associated with SCA vulnerabilities was affected. No other modules in the platform were impacted. The problem was resolved in 13.4 hours \(TTF\), resulting in a total window of exposure of 2.3 days \(WOE\) [\[2\]](https://gitlab.com/fluidattacks/universe/-/issues/18163). **Cause** A field that was previously used to display vulnerability information in the application was removed from the system’s API, but the platform’s interface was still trying to access it. This mismatch caused an error when loading certain weaknesses, which resulted in a blank screen [\[3\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/85968). **Solution** The platform was updated to stop using the removed field and to retrieve the necessary vulnerability data from the correct source. This change ensures that all information loads properly and prevents similar display errors in the future [\[4\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/85978). **Conclusion** In addition to discussing refactoring plans to prevent similar issues, the team agreed to implement a stricter validation process, ensuring that frontend dependencies are reviewed and adjusted before backend field removals. This will enhance communication and prevent similar disruptions in future releases. **UNHANDLED\_EXCEPTION <** **INFRASTRUCTURE\_ERROR**