Comparison Overview
Muscat Electronics LLC
Muscat Electronics LLC
P.O. Box 1009, Muscat, P.O. Box 1009, PC 114, OM
Last Update: 29/01/2026
Muscat Electronics LLC (ME) established in 1979 is part of the Al Yousef Group, plays a key role in the development of the nation by providing world class brands and services across industries to the citizens and residents of Oman. Our success is a reflection of our...
HARMAN International
400 Atlantic St, Stamford, 06901, US
Last Update: 10/09/2026
Headquartered in Stamford, Connecticut, HARMAN (harman.com) designs and engineers connected products and solutions for automakers, consumers, and enterprises worldwide, including connected car systems, audio and visual products, enterprise automation solutions; and serv...
Compliance Ranges Comparison
Muscat Electronics LLC
HARMAN International
Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Muscat Electronics LLC in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for HARMAN International in 2026.
Incident History - Muscat Electronics LLC (X = Date, Y = Severity)
Muscat Electronics LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HARMAN International (X = Date, Y = Severity)
HARMAN International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Muscat Electronics LLC
HARMAN International
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.