Comparison Overview
Kellogg Company

Kellogg Company
One Kellogg Square, Battle Creek, 49017, US
Last Update: 13/09/2026
At Kellanova, our vision is to be the world’s best performing snacks-led powerhouse, unleashing the full potential of our differentiated brands and our passionate people. Powered by our strategy to Differentiate, Drive & Deliver, we are a leading company in global snac...

Philip Morris International
Avenue de Rhodanie 50, Lausanne, CH, 1007
Last Update: 14/09/2026
Philip Morris International (PMI) is a leading international consumer goods company working to deliver a smoke-free future and evolving its portfolio for the long term to include products outside of the tobacco and nicotine sector. Since 2008, PMI has invested more than...
Compliance Ranges Comparison

Kellogg Company







Philip Morris International






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Kellogg Company in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Philip Morris International in 2026.
Incident History - Kellogg Company (X = Date, Y = Severity)
Kellogg Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Philip Morris International (X = Date, Y = Severity)
Philip Morris International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Kellogg Company

Philip Morris International
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)