Comparison Overview
John Crane Japan
John Crane Japan
2222 Kamitoyama, Ritto, 520-3084, JP
Last Update: 06/02/2026
世界の進歩を牽引しているプロセス産業ですが、そのプロセス産業の企業様方には、効率的な業務運営を維持するため、当社John Craneをご愛顧いただいています。当社の専門家たちは、お客様からの信頼を最大限に実現するノウハウを持ち合わせており、当社は、最新の技術を活用して、極めて重要な回転機器や課題の多い環境に対応するために必要なイノベーションを生み出しています。そして、お客様が必要としているときに、当社は迅速に応えることが可能です。また、100年にわたり重要な役割を果たしてきたJohn Craneは、グローバルな規模の産業で変化し続ける...
Aker Solutions
Oksenøyveien 8, Fornebu, NO-1360, NO
Last Update: 14/09/2026
Aker Solutions delivers integrated solutions, products and services to the global energy industry. We enable low-carbon oil and gas production and develop renewable solutions to meet future energy needs. By combining innovative digital solutions and predictable project ...
Compliance Ranges Comparison
John Crane Japan
Aker Solutions
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for John Crane Japan in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Aker Solutions in 2026.
Incident History - John Crane Japan (X = Date, Y = Severity)
John Crane Japan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aker Solutions (X = Date, Y = Severity)
Aker Solutions cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
John Crane Japan
Aker Solutions
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.