Comparison Overview
SC Johnson
SC Johnson
1525 Howe Street, Racine, 53403, US
Last Update: 08/09/2026
We’re SC Johnson, a family company at work for a better world™. We are a leading manufacturer of household cleaning products and products for home storage, air care, pest control, shoe care and professional products. SC Johnson’s high-quality products and iconic brands...
Colgate-Palmolive
300 Park Ave, New York, New York, US, 10022
Last Update: 06/09/2026
Make More Smiles. We are Colgate-Palmolive, a caring, innovative growth company that is reimagining a healthier future for all people, their pets and our planet. For over 200 years, we've poured our care into creating a future where everyone has more reasons to smile. C...
Compliance Ranges Comparison
SC Johnson
Colgate-Palmolive
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for SC Johnson in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Colgate-Palmolive in 2026.
Incident History - SC Johnson (X = Date, Y = Severity)
SC Johnson cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Colgate-Palmolive (X = Date, Y = Severity)
Colgate-Palmolive cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SC Johnson
Colgate-Palmolive
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.