Comparison Overview
Corteva Agriscience
Corteva Agriscience
9330 Zionsville Rd., Indianapolis, 46268, US
Last Update: 05/09/2026
Corteva Agriscience combines industry-leading innovations, high-touch customer engagement and operational execution to profitably deliver solutions for the world's most pressing agriculture challenges. Corteva generates advantaged market preference through its unique di...
Syngenta Group
Rosentalstrasse 67, Basel, 4002, CH
Last Update: 08/09/2026
To help feed 10 billion people while reducing emissions and improve biodiversity. This is our mission as the global agriculture technology leader. With over 56,000 employees in more than 90 countries and hundreds of thousands of agricultural partners worldwide, we are c...
Compliance Ranges Comparison
Corteva Agriscience
Syngenta Group
Benchmark & Cyber Underwriting Signals
Incidents vs Farming Industry Avg (This Year)
No incidents recorded for Corteva Agriscience in 2026.
Incidents vs Farming Industry Avg (This Year)
Syngenta Group has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Corteva Agriscience (X = Date, Y = Severity)
Corteva Agriscience cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Syngenta Group (X = Date, Y = Severity)
Syngenta Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Corteva Agriscience
Syngenta Group
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.