Comparison Overview
Telia Finance

Telia Finance
Stjärntorget, Solna, Stockholm County, 169 79, SE
Last Update: 29/12/2025
Telia Finance is an independent company acting as a finance engine for Telia Company, one of the world's biggest telecoms operators. We are a closely knit team of about 100 people who work flexibly and purposefully towards resolving customers' problems. If you ask u...

FactSet
43 Glover Ave, Norwalk, Connecticut, US, 06850
Last Update: 01/04/2026
FactSet creates flexible, open data and software solutions for tens of thousands of investment professionals around the world, providing instant access to financial data and analytics that investors use to make crucial decisions. For 40 years, through market changes a...
Compliance Ranges Comparison

Telia Finance







FactSet






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

Telia Finance

FactSet
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)