Comparison Overview
Acushnet Company
Acushnet Company
333 Bridge Street, Fairhaven, 02719, US
Last Update: 01/04/2026
NOTICE: It has come to our attention that online scammers are impersonating Acushnet Company associates and contacting users on various online platforms, including Indeed and LinkedIn. To protect yourself, please note the following: Legitimate Communication: All legi...
Dräger
Moislinger Allee 53-55, Lübeck, 23552, DE
Last Update: 09/09/2026
Dräger is an international leader in the fields of medical and safety technology. The family-owned company was founded in Lübeck, Germany, in 1889. The company’s long-term success is based on the four key strengths of its value-driven culture: customer intimacy, profess...
Compliance Ranges Comparison
Acushnet Company
Dräger
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Acushnet Company in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Dräger in 2026.
Incident History - Acushnet Company (X = Date, Y = Severity)
Acushnet Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dräger (X = Date, Y = Severity)
Dräger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Acushnet Company
Dräger
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.