Comparison Overview
Ross Stores, Inc.
Ross Stores, Inc.
5130 Hacienda Drive, Dublin, CA, US, 94568
Last Update: 12/09/2026
For the last 40+ years, Ross Stores, Inc. has grown from a six-store chain into an $21.1 billion, Fortune 500 Company. We operate our off-price businesses in a way that keeps costs low so we can pass the savings to our customers. We continue to open new stores and our s...
noon
Building B11 King Khalid International Airport, The Business Front, Riyadh , KSA, SA, 13412
Last Update: 07/09/2026
noon is a digital ecosystem of products and services that are built in the region. Our vision is to become the engine of efficiency and convenience for the people we serve. We will elevate the quality of life by inspiring people with what we built and how we built it. ...
Compliance Ranges Comparison
Ross Stores, Inc.
noon
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Ross Stores, Inc. in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for noon in 2026.
Incident History - Ross Stores, Inc. (X = Date, Y = Severity)
Ross Stores, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - noon (X = Date, Y = Severity)
noon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ross Stores, Inc.
noon
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.