Comparison Overview
Golden Corral Corporation

Golden Corral Corporation
5400 Trinity Road, Ste. 309, Raleigh, 27607, US
Last Update: 03/04/2026
The right place. The best people. Golden Corral, a leading chain restaurant company, is just the place for people with a focus on being the best. Opening our doors in 1973, our history is marked by innovation, growth and caring about people. From day one, we establis...

P.F. Chang's
8377 E Hartford Dr, #200, Scottsdale, Arizona, US, 85255
Last Update: 05/09/2026
P.F. Chang’s is a restaurant concept that honors the 2,000-year-old Asian tradition of wok cooking and believes in making food from scratch every day in every restaurant. Since inception, P.F. Chang’s chefs hand-roll dim sum, hand chop and slice all vegetables and meat...
Compliance Ranges Comparison

Golden Corral Corporation







P.F. Chang's






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Golden Corral Corporation in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for P.F. Chang's in 2026.
Incident History - Golden Corral Corporation (X = Date, Y = Severity)
Golden Corral Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - P.F. Chang's (X = Date, Y = Severity)
P.F. Chang's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Golden Corral Corporation

P.F. Chang's
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.