Comparison Overview
Chattanooga Gas

Chattanooga Gas
2207 Olan Mills Drive, Chattanooga, 37421, US
Last Update: 04/04/2026
With roots that extend back to the late 1800s, Chattanooga Gas today provides retail natural gas sales and transportation services to approximately 60,000 customers in Hamilton and Bradley counties in southeast Tennessee.

Enedis
4 place de la Pyramide, Puteaux, FR, 92800
Last Update: 13/09/2026
Enedis est le gestionnaire du réseau public de distribution d’électricité sur 95 % du territoire français continental. Ses 38 859 collaborateurs assurent chaque jour l’exploitation, l’entretien et le développement de près de 1,3 million de kilomètres de réseau. Raccord...
Compliance Ranges Comparison

Chattanooga Gas







Enedis






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Chattanooga Gas in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Enedis in 2026.
Incident History - Chattanooga Gas (X = Date, Y = Severity)
Chattanooga Gas cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Enedis (X = Date, Y = Severity)
Enedis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Chattanooga Gas

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