Comparison Overview
Equifax UK

Equifax UK
1 Angel Court, London, EC2R 7HJ, GB
Last Update: 03/04/2026
Anything's possible when you ask, what if? For more information, please visit www.equifax.co.uk/business/en_gb Equifax Limited Equifax Limited is registered in England with Registered No. 2425920. Registered Office: 1 Angel Court, London, EC2R 7HJ. Equifax Limited is...

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

Equifax UK







FactSet






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Equifax UK in 2026.
Incidents vs Financial Services Industry Avg (This Year)
FactSet has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Equifax UK (X = Date, Y = Severity)
Equifax UK 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

Equifax UK

FactSet
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.