Comparison Overview
Brioni
Brioni
*, Rome, 00187, IT
Last Update: 17/03/2026
Since 1945, the Brioni style is one of effortless modern elegance. It stems from excellence through in-house sartorial savoir-faire and continuous research in exceptional materials. In addition to its state-of-the-art Bespoke service, the House offers unparalleled, made...
Tiffany & Co.
727 5th Ave, New York, 10022, US
Last Update: 05/09/2026
In 1837 Charles Lewis Tiffany founded his company in New York City where his store was soon acclaimed as the palace of jewels for its exceptional gemstones. Since then TIFFANY & CO. has become synonymous with elegance, innovative design, fine craftsmanship and creative ...
Compliance Ranges Comparison
Brioni
Tiffany & Co.
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Brioni in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
Tiffany & Co. has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Brioni (X = Date, Y = Severity)
Brioni cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tiffany & Co. (X = Date, Y = Severity)
Tiffany & Co. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Brioni
Tiffany & Co.
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.