Comparison Overview
Pet Food Experts

Pet Food Experts
175 Main St, None, Pawtucket, Rhode Island, US, 02860
Last Update: 10/03/2026
Pet Food Experts (PFX) is the leading pet specialty distributor in the U.S., serving over 10,000 pet retailers nationwide. With decades of industry expertise, we’re more than a distributor—we’re a trusted partner committed to strengthening the pet specialty community. B...

Wesco
225 W Station Square Dr, Pittsburgh, Pennsylvania, US, 15219
Last Update: 12/08/2026
At Wesco, we believe life should run smoothly. As a leading provider of business-to-business distribution, logistics services and supply chain solutions, we create a world that you can depend on. Harnessing 100 years of ingenuity and expertise, we increase profitability...
Compliance Ranges Comparison

Pet Food Experts







Wesco






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

Pet Food Experts

Wesco
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.