Comparison Overview
Lone Peak Physical Therapy

Lone Peak Physical Therapy
PO Box 160010, Big Sky, Montana, 59716-0000, US
Last Update: 22/04/2026
Human movement is our specialty. Whether you are an elite athlete, a "weekend warrior", or an injured worker, how efficiently you move dramatically affects how well you function. We know that the better you move, the better you will feel, and ultimately the better you...

Smart Fit
Avenida Paulista 1294, São Paulo, BR
Last Update: 01/04/2026
Somos o Grupo Smart Fit, a força que ativa o seu potencial. Um ecossistema em constante evolução que une tecnologia, propósito e performance para transformar o fitness, e a vida das pessoas, em movimento real. Com mais de 22 mil colaboradores e colaboradoras em 16 país...
Compliance Ranges Comparison

Lone Peak Physical Therapy







Smart Fit






Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Lone Peak Physical Therapy in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Smart Fit in 2026.
Incident History - Lone Peak Physical Therapy (X = Date, Y = Severity)
Lone Peak Physical Therapy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Smart Fit (X = Date, Y = Severity)
Smart Fit cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Lone Peak Physical Therapy

Smart Fit
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.