Comparison Overview
Breas Medical
Breas Medical
undefined, undefined, undefined, undefined, SE
Last Update: 30/12/2025
About Breas Medical Founded in 1991 in Gothenburg, Sweden, Breas has become one of the global leaders in Home Mechanical Ventilation, Airway Clearance, Sleep therapy and Connected Care. Our vision is to provide Better breathing and quality of life to respiratory patient...
BD
1 Becton Drive, Franklin Lakes, 07417, US
Last Update: 13/09/2026
BD is one of the world's largest pure-play medical technology companies with a Purpose of advancing the world of health™ by driving innovation across medical essentials, connected care, biopharma systems and interventional. The company supports those on the frontlines o...
Compliance Ranges Comparison
Breas Medical
BD
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Breas Medical in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for BD in 2026.
Incident History - Breas Medical (X = Date, Y = Severity)
Breas Medical cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BD (X = Date, Y = Severity)
BD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Breas Medical
BD
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.