Comparison Overview
Pharmaceutical Commerce
Pharmaceutical Commerce
485 Route 1 South, Iselin, 08330, US
Last Update: 07/03/2026
Pharmaceutical Commerce is dedicated to the commercial operations of the North American pharmaceutical industry. Four times a year, its 16,000 executive readers get the latest information and analysis commercial operations, marketing/sales best practices, supply chain m...
Bristol Myers Squibb
3401 Princeton Pike, Lawrence Township, 08648, US
Last Update: 09/09/2026
At Bristol Myers Squibb, we work every day to transform patients’ lives through science. That work inspires some of the most interesting, meaningful, and life-changing careers you’ll experience. Join us and pursue innovative ideas alongside some of the brightest minds i...
Compliance Ranges Comparison
Pharmaceutical Commerce
Bristol Myers Squibb
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Pharmaceutical Commerce in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Bristol Myers Squibb in 2026.
Incident History - Pharmaceutical Commerce (X = Date, Y = Severity)
Pharmaceutical Commerce cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bristol Myers Squibb (X = Date, Y = Severity)
Bristol Myers Squibb cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pharmaceutical Commerce
Bristol Myers Squibb
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.