Comparison Overview
Tigo Colombia

Tigo Colombia
Medellín, Bogotá, Cali, Barranquilla, Cartagena, Pereira, Manizales, Bucaramanga, Palmira, Valledupar, Villavicencio, Santa Marta, Montería, Tuluá, Tolú, Sincelejo, Cúcuta, Barrancabermeja, Armenia, Boyacá, Ibagué, Huila y Caquetá., Colombia 050022, CO, Medellín, Bogotá, Cali, Barranquilla, Cartagena, Pereira, Manizales, Bucaramanga, Palmira, Valledupar, Villavicencio, Santa Marta, Montería, Tuluá, Tolú, Sincelejo, Cúcuta, Barrancabermeja, Armenia, Boyacá, Ibagué, Huila y Caquetá., Colombia 050022, CO
Last Update: 25/04/2026
Tigo is one of the most relevant telecommunications service operators in Colombia, whose main purpose is to connect more and more Colombians through digital highways in fixed and mobile networks and a differential value offer, promoting innovation as a DNA for the organ...

SFR
16, Rue du Général Alain de Boissieu, Paris, 75015, FR
Last Update: 07/09/2026
SFR is the number one alternative telecoms operator in France. SFR is also an operator providing a comprehensive range of services meeting the expectations of private and business customers alike, offering them the best of the digital world. At year-end 2011, the total ...
Compliance Ranges Comparison

Tigo Colombia







SFR






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Tigo Colombia in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
SFR has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Tigo Colombia (X = Date, Y = Severity)
Tigo Colombia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SFR (X = Date, Y = Severity)
SFR cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Tigo Colombia

SFR
FAQ
Latest Global CVEs
DocsGPT through 0.20.0 posts OAuth connector session tokens to a wildcard target origin in the callback-status endpoint without validating sender origin. Attackers can obtain session tokens and provider account emails by acting as window.opener during OAuth authorization, then use tokens to disconnect victims' cloud storage connectors.
- https://github.com/arc53/DocsGPT
- https://github.com/arc53/DocsGPT/blob/c36b0af17037449f34449efa97da82becfc9492d/docsgpt/api/connector/routes.py#L344-L366
- https://github.com/arc53/DocsGPT/blob/c36b0af17037449f34449efa97da82becfc9492d/docsgpt/api/connector/routes.py#L515-L527
- https://github.com/arc53/DocsGPT/blob/c36b0af17037449f34449efa97da82becfc9492d/frontend/src/components/ConnectorAuth.tsx#L57-L80
- https://github.com/arc53/DocsGPT/issues/2766
- https://www.vulncheck.com/advisories/docsgpt-through-0.20.0-oauth-token-disclosure-via-wildcard-postmessage
DevSpace through 6.3.21 fails to reject parent-directory segments in tar entry names from the in-pod sync stream. Attackers operating a malicious container can stream tar entries with traversal sequences to write arbitrary files on the developer workstation, enabling code execution.
- https://github.com/devspace-sh/devspace
- https://github.com/devspace-sh/devspace/blob/7f272dcf90653fa9b42bc4347f7f3f9a52b0e8b5/pkg/devspace/sync/tar.go#L68-L82
- https://github.com/devspace-sh/devspace/blob/7f272dcf90653fa9b42bc4347f7f3f9a52b0e8b5/pkg/devspace/sync/util.go#L9-L11
- https://github.com/devspace-sh/devspace/issues/3290
- https://www.vulncheck.com/advisories/devspace-through-6.3.21-path-traversal-via-tar-extraction
Refly through 1.1.0 contains a server-side request forgery vulnerability in the POST /v1/misc/scrape endpoint that fetches caller-supplied URLs without validating the scheme, host, or resolved address. Authenticated attackers can make the backend issue requests to loopback, private, and link-local addresses including cloud metadata services to read page titles and descriptions of internal resources.
- https://github.com/refly-ai/refly
- https://github.com/refly-ai/refly/blob/77fb0ca184251bba7380cbac2dbdf7a6c9944652/apps/api/src/modules/misc/misc.controller.ts#L38-L43
- https://github.com/refly-ai/refly/blob/77fb0ca184251bba7380cbac2dbdf7a6c9944652/packages/utils/src/scrape-weblink.ts
- https://github.com/refly-ai/refly/issues/2280
- https://www.vulncheck.com/advisories/refly-through-1.1.0-server-side-request-forgery-via-scrape-endpoint
GrowthBook through 5.0.1 returns unredacted fact table definitions including raw warehouse SQL in payloads served by unauthenticated public report and experiment endpoints. Attackers with knowledge of a publicly shared report or experiment identifier can read internal data warehouse query text, schema, table names, filter values and datasource identifiers.
- https://github.com/growthbook/growthbook
- https://github.com/growthbook/growthbook/blob/57d07471b137eb43d9bfb1613d0a1203d21fef88/packages/back-end/src/app.ts#L391-L409
- https://github.com/growthbook/growthbook/blob/57d07471b137eb43d9bfb1613d0a1203d21fef88/packages/back-end/src/services/reports.ts#L880-L890
- https://github.com/growthbook/growthbook/issues/6541
- https://www.vulncheck.com/advisories/growthbook-through-5.0.1-information-disclosure-via-public-endpoints
Flowable flowable-engine through 8.0.0 contains an XML external entity injection vulnerability in ProcessDiagramLayoutFactory.parseXml() that fails to disable external entity resolution when parsing deployed BPMN resources. Attackers with process deployment privileges can embed DOCTYPE declarations with external entities in BPMN files to read arbitrary local files or trigger requests to internal network endpoints when diagram layout is computed.
- https://github.com/flowable/flowable-engine
- https://github.com/flowable/flowable-engine/blob/0779d68e5a3385b74d8acb8bc37901ff54513249/modules/flowable-engine/src/main/java/org/flowable/engine/impl/bpmn/diagram/ProcessDiagramLayoutFactory.java#L101-L118
- https://github.com/flowable/flowable-engine/blob/0779d68e5a3385b74d8acb8bc37901ff54513249/modules/flowable5-engine/src/main/java/org/activiti/engine/impl/bpmn/diagram/ProcessDiagramLayoutFactory.java#L97-L114
- https://github.com/flowable/flowable-engine/issues/4216
- https://www.vulncheck.com/advisories/flowable-flowable-engine-through-8.0.0-xxe-via-processdiagramlayoutfactory