Comparison Overview
HP Public Sector
HP Public Sector
Palo Alto, California, US, 94304
Last Update: 03/04/2026
HP Public Sector delivers secure, sustainable, and AI-powered technology solutions that accelerate modernization across U.S. federal, state, local, and education agencies. From mission-critical devices and managed services to hybrid work infrastructure and cybersecurity...
NEC Corporation
7-1, Shiba 5-chome, Tokyo, 108-8001, JP
Last Update: 08/09/2026
NEC Corporation has established itself as a leader in the integration of IT and network technologies while promoting the brand statement of “Orchestrating a brighter world.” NEC enables businesses and communities to adapt to rapid changes taking place in both society an...
Compliance Ranges Comparison
HP Public Sector
NEC Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for HP Public Sector in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for NEC Corporation in 2026.
Incident History - HP Public Sector (X = Date, Y = Severity)
HP Public Sector cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NEC Corporation (X = Date, Y = Severity)
NEC Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
HP Public Sector
NEC Corporation
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.