Resolved after 1 day 3 hours, affecting CapaOne Privileges, on February 19, 2026.
This issue is resolved in Agent 139, which is correctly signed and should no longer trigger false-positive detections.
Affected components
Update timeline
- 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.
- monitoring Feb 19, 2026, 11:06 AM UTC
A fix has been implemented and we are monitoring the results.
- 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.
Your product runs on more than CapaSystems CapaOne
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services