Comparison Overview
Telenor Connexion

Telenor Connexion
N/A
Last Update: 17/12/2025
Our headquarters and tech center is in Sweden with sales representation in the UK, US, the Nordics, Germany, South Africa, Japan, Korea, China, Thailand, Singapore and Malaysia. We are proud of our Nordic business heritage and a commitment to open and transparent operat...

Telia
Stjärntorget 1, SOLNA, SE-169 94, SE
Last Update: 15/09/2026
Our 15 000 talented colleagues serve millions of customers every day in one of the world’s most connected regions. With a strong connectivity base, we’re the hub in the digital ecosystem, empowering people, companies and societies to stay in touch with everything that m...
Compliance Ranges Comparison

Telenor Connexion







Telia






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

Telenor Connexion

Telia
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)