CapaSystems CapaOne incident

CapaOne Agent 132 is not signed correctly

Major Resolved View vendor source →

CapaSystems CapaOne experienced a major incident on February 19, 2026 affecting CapaOne Privileges, lasting 1d 3h. The incident has been resolved; the full update timeline is below.

Started
Feb 19, 2026, 08:58 AM UTC
Resolved
Feb 20, 2026, 12:41 PM UTC
Duration
1d 3h
Detected by Pingoru
Feb 19, 2026, 08:58 AM UTC

Affected components

CapaOne Privileges

Update timeline

  1. identified Feb 19, 2026, 08:58 AM UTC

    We have identified that Agent 132 is not signed correctly. Because of this, the agent may be flagged as a potential virus by antivirus or security software. The issue is related to the code-signing of the agent and is currently being investigated. An updated, correctly signed version will be provided.

  2. monitoring Feb 19, 2026, 11:06 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 20, 2026, 12:41 PM UTC

    This issue is resolved in Agent 139, which is correctly signed and should no longer trigger false-positive detections.