Comparison Overview
MOON POWER Bulgaria
MOON POWER Bulgaria
Business Park Sofia, Building 5A, Sofia, 1766, BG
Last Update: 15/12/2025
MOON е иновативен бранд, част от портфолиото на Порше БГ, дъщерна компания на Porsche Holding Залцбург, който предлага интелигентни и базирани на потребностите енергийни решения предназначени, както за дома, така и за търговски цели. Марката MOON твърдо застава зад Пари...
National Grid
1–3 Strand, London, WC2N 5EH, GB
Last Update: 09/09/2026
We power the lives of millions of people across Britain, New York and Massachusetts, moving energy from where it’s made to the communities that need it, every single day. In the UK, people connect with the electricity they need to live, work, build and play through our...
Compliance Ranges Comparison
MOON POWER Bulgaria
National Grid
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for MOON POWER Bulgaria in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for National Grid in 2026.
Incident History - MOON POWER Bulgaria (X = Date, Y = Severity)
MOON POWER Bulgaria cyber incidents detection timeline including parent company and subsidiaries.
Incident History - National Grid (X = Date, Y = Severity)
National Grid cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MOON POWER Bulgaria
National Grid
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.