Comparison Overview
Flora & Fauna
Flora & Fauna
3/91 Campbell St, Surry Hills, 2010, AU
Last Update: 29/03/2026
Flora & Fauna is Australia’s kindest store — your trusted destination for 100% vegan, cruelty-free and low-impact products. From skincare to snacks, baby care to bathroom swaps, everything we stock meets strict ethical standards. No greenwashing, no nasties — just bet...
Target
1000 Nicollet Mall, Minneapolis, 55403, US
Last Update: 12/09/2026
Target is one of the world’s most recognized brands and one of America’s leading retailers. We make Target our guests’ preferred shopping destination by offering outstanding value, inspiration, innovation and an exceptional guest experience that no other retailer can de...
Compliance Ranges Comparison
Flora & Fauna
Target
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Flora & Fauna in 2026.
Incidents vs Retail Industry Avg (This Year)
Target has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Flora & Fauna (X = Date, Y = Severity)
Flora & Fauna cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Target (X = Date, Y = Severity)
Target cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Flora & Fauna
Target
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.