Comparison Overview
John West Holland B.V.
John West Holland B.V.
Herculesplein 215, Utrecht, 3584 AA, NL
Last Update: 10/02/2026
Al sinds 1857 vangt John West wilde vis van de beste kwaliteit. Bij John West vinden we dat iedereen van het goede van vis moet kunnen genieten. Vis is namelijk van nature rijk aan eiwitten, goede vetten en vitamines. Het is daarmee de perfecte basis voor een lekker act...
McCain Foods
439 King Street West, Toronto, ON, CA, M5V 1K4
Last Update: 01/04/2026
At McCain, we believe food plays an important role in people’s lives, with the power to bring individuals, families, and communities together. As a privately owned family company with over 67 years of experience, a presence in over 160 countries, and a global team of...
Compliance Ranges Comparison
John West Holland B.V.
McCain Foods
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for John West Holland B.V. in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for McCain Foods in 2026.
Incident History - John West Holland B.V. (X = Date, Y = Severity)
John West Holland B.V. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - McCain Foods (X = Date, Y = Severity)
McCain Foods cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
John West Holland B.V.
McCain Foods
FAQ
Latest Global CVEs
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). A low-privileged authenticated user can send a specially crafted request to a Kibana machine learning feature, causing the server to exhaust available memory and become unavailable to all users.
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead to denial of service via Excessive Allocation (CAPEC-130). An authenticated attacker with low-privilege access can trigger a denial of service condition in Kibana by sending a specially crafted, oversized request payload. Processing this user-supplied input requires resource-intensive memory allocation that can exhaust the available heap memory in the Kibana process, causing it to crash and become unavailable to all users.
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via user-supplied identifiers that reference scheduled query result data from Kibana Spaces the requester is not authorized to access.
Incorrect Authorization (CWE-863) in Kibana can lead to integrity compromise of Machine Learning audit and notification records via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). A vulnerability exists in Kibana's Machine Learning functionality where a Machine Learning management endpoint performs an insufficient authorization check. The endpoint validates only a coarse privilege level but does not verify that the requesting user has access to the specific Machine Learning job or notification resources provided in the request. As a result, a low-privileged user with Machine Learning access in any Kibana space can manipulate Machine Learning audit and notification records for arbitrary jobs—including jobs in other spaces or belonging to other users—by leveraging Kibana's internally elevated credentials to write to restricted Machine Learning system indices that the user cannot access directly.
Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via a specially crafted search request submitted by a low-privileged authenticated user. A user with read-level index access can submit a request that triggers unbounded recursive processing within the Elasticsearch query evaluation component, causing a fatal error that terminates the affected node. In single-node deployments, this results in complete service outage; in multi-node clusters, it causes repeated node restarts and sustained availability degradation.