Comparison Overview
Atlanta Gas Light
Atlanta Gas Light
10 Peachtree Place, Atlanta, GA, 30309, US
Last Update: 08/02/2026
Atlanta Gas Light is the largest natural gas distributor in the Southeast. It provides delivery service to approximately 1.55 million residential, commercial and industrial customers in Georgia. Atlanta Gas Light's role in Georgia's deregulated environment includes: ...
Correos
Calle del Conde de Peñalver, 19, Madrid, 28006, ES
Last Update: 03/09/2026
Somos la empresa líder en comunicaciones físicas, digitales y de paquetería. Nuestra misión es prestar un servicio integral de calidad, ofreciendo soluciones y servicios en toda la cadena de valor del ecommerce con el objetivo de facilitar la vida a nuestros clientes. D...
Compliance Ranges Comparison
Atlanta Gas Light
Correos
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Atlanta Gas Light in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Correos in 2026.
Incident History - Atlanta Gas Light (X = Date, Y = Severity)
Atlanta Gas Light cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Correos (X = Date, Y = Severity)
Correos cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Atlanta Gas Light
Correos
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.