Comparison Overview
Vineyard Wind
Vineyard Wind
700 Pleasant Street, New Bedford, MA 02740, MA, 02740, US
Last Update: 03/04/2026
Vineyard Wind is well underway in developing the nation's first utility-scale offshore wind energy project over 15 miles off the coast of Massachusetts. The project will generate clean, renewable, cost-competitive energy for over 400,000 homes and businesses across the...
Constellation
1310 Point Street, Baltimore, 21231, US
Last Update: 09/09/2026
Constellation Energy Corporation (Nasdaq: CEG), a Fortune 200 company headquartered in Baltimore, is the nation’s largest producer of reliable, emissions-free energy and a leading energy supplier to businesses, homes and public sector customers nationwide, including thr...
Compliance Ranges Comparison
Vineyard Wind
Constellation
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Vineyard Wind in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Constellation in 2026.
Incident History - Vineyard Wind (X = Date, Y = Severity)
Vineyard Wind cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Constellation (X = Date, Y = Severity)
Constellation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Vineyard Wind
Constellation
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.