Comparison Overview
SmartestEnergy US

SmartestEnergy US
110 W Fayette St, Suite 400, Syracuse, New York, US, 13202
Last Update: 05/04/2026
We are a people-centred energy retail partner and wholesale commodity trader. We supply flexible, reliable and creative energy solutions to businesses in the United States, continually expanding our footprint.

Exelon
10 S. Dearborn, Chicago, 60603, US
Last Update: 05/09/2026
Exelon Corporation (Nasdaq: EXC) is one of the nation’s largest utility companies, serving more than 10 million customers through six fully regulated utilities. We believe that reliable and affordable energy is essential to a brighter, more sustainable future. We are a ...
Compliance Ranges Comparison

SmartestEnergy US







Exelon






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

SmartestEnergy US

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