Comparison Overview
Burlington Stores, Inc.
Burlington Stores, Inc.
2006 Route 130, Burlington, NJ, US, 08016
Last Update: 18/09/2026
Burlington Stores, Inc., headquartered in New Jersey, is a nationally recognized off-price retailer. Burlington is a Fortune 500 company and its common stock is traded on the New York Stock Exchange under the ticker symbol “BURL.” The Company operates more than 1000 sto...
Ulta Beauty
1000 Remington Blvd, Bolingbrook, 60440, US
Last Update: 02/04/2026
At Ulta Beauty (NASDAQ: ULTA), the possibilities are beautiful. Ulta Beauty is the largest U.S. beauty retailer and the premier beauty destination for cosmetics, fragrance, skin care products, hair care products and salon services. In 1990, the Company reinvented the be...
Compliance Ranges Comparison
Burlington Stores, Inc.
Ulta Beauty
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Burlington Stores, Inc. in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Ulta Beauty in 2026.
Incident History - Burlington Stores, Inc. (X = Date, Y = Severity)
Burlington Stores, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ulta Beauty (X = Date, Y = Severity)
Ulta Beauty cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Burlington Stores, Inc.
Ulta Beauty
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.