Comparison Overview
Vintage Nurseries
Vintage Nurseries
27920 McCombs Avenue, Wasco, 93280, US
Last Update: 20/01/2026
Vintage Nurseries is the industry's leading provider of dormant field-grown benchgrafts, greenhouse-grown benchgrafts, dormant rootstock rootings and other vineyard-related products to wine grape, table grape and juice grape growers across the country. Vintage Nurserie...
Syngenta
Rosentalstrasse 67, Basel, Basel, CH, 4002
Last Update: 08/09/2026
Syngenta is one of the world’s leading agriculture companies. Our ambition is to help safely feed the world while taking care of the planet. We aim to improve the sustainability, quality and safety of agriculture with world class science and innovative crop solutions. ...
Compliance Ranges Comparison
Vintage Nurseries
Syngenta
Benchmark & Cyber Underwriting Signals
Incidents vs Farming Industry Avg (This Year)
No incidents recorded for Vintage Nurseries in 2026.
Incidents vs Farming Industry Avg (This Year)
No incidents recorded for Syngenta in 2026.
Incident History - Vintage Nurseries (X = Date, Y = Severity)
Vintage Nurseries cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Syngenta (X = Date, Y = Severity)
Syngenta cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Vintage Nurseries
Syngenta
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.