Fluid Attacks incident

Error generating vulnerabilities CSV export

Notice Resolved View vendor source →

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

Started
Oct 08, 2025, 06:38 PM UTC
Resolved
Oct 08, 2025, 08:43 PM UTC
Duration
2h 4m
Detected by Pingoru
Oct 08, 2025, 06:38 PM UTC

Affected components

Platform

Update timeline

  1. identified Oct 08, 2025, 06:38 PM UTC

    Users are experiencing issues when attempting to export the Vulnerabilities CSV file. The process fails to complete, preventing the report generation.

  2. resolved Oct 08, 2025, 08:43 PM UTC

    The incident has been resolved, and the vulnerabilities CSV export feature is now working correctly.

  3. postmortem Oct 08, 2025, 10:56 PM UTC

    **Impact** At least one user experienced issues when trying to generate a Vulnerabilities CSV report. The issue started on UTC-5 25-10-07 17:54 and was reactively discovered 17.5 hours \(TTD\) later by a client who reported through our help desk [\[1\]](https://help.fluidattacks.com/agent/fluid4ttacks/fluid-attacks/tickets/details/944043000049838507) that the process stayed stuck in a “Processing file” state and never finished. This issue affected all groups that had vulnerabilities marked with the source `CUSTOMER`. The problem was resolved in 2.6 hours \(TTF\), resulting in a total window of exposure of 20.1 hours \(WOE\) [\[2\]](https://gitlab.com/fluidattacks/universe/-/issues/18219). **Cause** A specific value called `CUSTOMER` was removed from the system configuration used to identify the source of vulnerabilities. This value was deleted as part of a cleanup process, assuming it was no longer needed. However, the platform still had some vulnerabilities using that value, and a function tried to read it when generating the CSV report. Since the value no longer existed, the process failed and caused the file generation to stop [\[3\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/86156/diffs). **Solution** The `CUSTOMER` value was temporarily added back to the system so reports could be generated correctly again. A migration will be done soon to remove all vulnerabilities using this outdated value, allowing it to be safely deleted later [\[4\]](https://gitlab.com/fluidattacks/universe/-/merge_requests/86219/diffs). **Conclusion** Extra checks were added to ensure that all possible source values are correctly recognized by the system. This will prevent similar errors in future updates or cleanups. **INCOMPLETE\_PERSPECTIVE < MISSING\_TEST**