Comparison Overview
GIZ ConoSur (Argentina, Chile, Perú)

GIZ ConoSur (Argentina, Chile, Perú)
N/A
Last Update: 13/03/2026
La cooperación alemana para el desarrollo, implementada por la Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH, asiste al Gobierno de la República Federal de Alemania para alcanzar sus objetivos en los ámbitos de la cooperación internacional para el d...

COTO
Ciudad Autónoma de Buenos Aires, AR
Last Update: 14/09/2026
¿Sabés lo importante que es para nosotros que formes parte de COTO? Te proponemos superarte con proyectos arquitectónicos increíbles como, por ejemplo, la construcción de un mega centro comercial, o profesionalizarte en Comercio Exterior interactuando con los mercados ...
Compliance Ranges Comparison

GIZ ConoSur (Argentina, Chile, Perú)







COTO






Benchmark & Cyber Underwriting Signals
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for GIZ ConoSur (Argentina, Chile, Perú) in 2026.
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for COTO in 2026.
Incident History - GIZ ConoSur (Argentina, Chile, Perú) (X = Date, Y = Severity)
GIZ ConoSur (Argentina, Chile, Perú) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - COTO (X = Date, Y = Severity)
COTO cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

GIZ ConoSur (Argentina, Chile, Perú)

COTO
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.