Comparison Overview
Sol de Janeiro
Sol de Janeiro
551 5th Ave, None, New York, NY, US, 10176
Last Update: 12/02/2026
Inspired by the power and warmth of the Brazilian spirit, Sol de Janeiro stands for ultimate self-love and celebration. Embracing the authentic Brazilian beauty philosophy of loving and flaunting your body, Sol de Janeiro was founded in 2015. The brand’s award-winning c...
Amplifon
Via Ripamonti 133, Milan, 20141, IT
Last Update: 31/03/2026
As the global leader in the hearing care retail industry, we have been changing the lives of millions of customers across the globe since 1950. With stores and offices spanning across 26 countries and a team of 20,300 dedicated professionals, we take pride in setting th...
Compliance Ranges Comparison
Sol de Janeiro
Amplifon
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Health and Personal Care Products Industry Avg (This Year)
No incidents recorded for Sol de Janeiro in 2026.
Incidents vs Retail Health and Personal Care Products Industry Avg (This Year)
No incidents recorded for Amplifon in 2026.
Incident History - Sol de Janeiro (X = Date, Y = Severity)
Sol de Janeiro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amplifon (X = Date, Y = Severity)
Amplifon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sol de Janeiro
Amplifon
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.