Episource is now a part of Optum. To stay up-to-date with news please connect with us at Optum.com.
Líder em transformação digital nos mercados de Customer Experience e Debt Collection na América Latina. Combinamos tecnologia, inteligência e excelência operacional para entregar soluções completas que antecipam as necessidades dos nossos Clientes. São mais de 530 milhões de interações anuais, metade em canais digitais, para um portfólio de 60+ clientes. Siga-nos e acompanhe como transformamos experiências em resultados.
Security & Compliance Standards Overview
Episource has 55.95% fewer incidents than the average of same-industry companies with at least one recorded incident.
No incidents recorded for AlmavivA Experience in 2026.
Episource cyber incidents detection timeline including parent company and subsidiaries
AlmavivA Experience cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
Improper validation of specified type of input in M365 Copilot allows an unauthorized attacker to disclose information over a network.
Improper access control in Azure Front Door (AFD) allows an unauthorized attacker to elevate privileges over a network.
Azure Entra ID Elevation of Privilege Vulnerability
Moonraker is a Python web server providing API access to Klipper 3D printing firmware. In versions 0.9.3 and below, instances configured with the "ldap" component enabled are vulnerable to LDAP search filter injection techniques via the login endpoint. The 401 error response message can be used to determine whether or not a search was successful, allowing for brute force methods to discover LDAP entries on the server such as user IDs and user attributes. This issue has been fixed in version 0.10.0.
Runtipi is a Docker-based, personal homeserver orchestrator that facilitates multiple services on a single server. Versions 3.7.0 and above allow an authenticated user to execute arbitrary system commands on the host server by injecting shell metacharacters into backup filenames. The BackupManager fails to sanitize the filenames of uploaded backups. The system persists user-uploaded files directly to the host filesystem using the raw originalname provided in the request. This allows an attacker to stage a file containing shell metacharacters (e.g., $(id).tar.gz) at a predictable path, which is later referenced during the restore process. The successful storage of the file is what allows the subsequent restore command to reference and execute it. This issue has been fixed in version 4.7.0.
