Comparison Overview
Ajinomoto Türkiye
Ajinomoto Türkiye
AOS 55. Sokak, Maslak, 34485, TR
Last Update: 06/01/2026
The Ajinomoto Group is a pioneer company in manufacturing food products and producing amino acids based on the founding aspiration of “Eat Well, Live Well”. Established in 1909, Ajinomoto is the founder of Umami. Ajinomoto aims to improve food culture and human health t...
PT SMART Tbk
Jl. M.H. Thamrin No. 51, Jakarta, 10350, ID
Last Update: 14/09/2026
PT SMART Tbk (SMART) / Sinar Mas Agribusiness and Food adalah salah satu perusahaan publik produk konsumen berbasis kelapa sawit yang terintegrasi dan terkemuka di Indonesia yang berkomitmen pada produksi minyak sawit yang berkelanjutan. Perkebunan kelapa sawit SMART m...
Compliance Ranges Comparison
Ajinomoto Türkiye
PT SMART Tbk
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Ajinomoto Türkiye in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for PT SMART Tbk in 2026.
Incident History - Ajinomoto Türkiye (X = Date, Y = Severity)
Ajinomoto Türkiye cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PT SMART Tbk (X = Date, Y = Severity)
PT SMART Tbk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ajinomoto Türkiye
PT SMART Tbk
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.