Comparison Overview
Kraken Technologies Japan

Kraken Technologies Japan
六本木1−6−1, 港区, 106-6028, JP
Last Update: 02/09/2026
Krakenは、エネルギー業界向けの最も信頼され、実績あるオペレーティングシステムです。Utility-Grade AI™と深い業界知見を活かし、ユーティリティ事業者の業務変革とエネルギー移行を支援しています。家庭・法人から大規模産業顧客まで、世界9,000万以上のアカウントをサポートし、最大40%の業務効率化、顧客満足度を3倍に改善といった成果を実現。東京ガス、EDF Energy、E.ON Next、Octopus Energy、Origin、Plenitude、National Gridなど、世界の主要ユーティリティに採用されて...

Amazon Fulfillment Technologies & Robotics
300 Riverpark Drive, North Reading, MA, US, 01864
Last Update: 15/09/2026
On the Fulfillment Technologies & Robotics Team, we build dynamic partnerships between people and intelligent machines. This intricate collaboration helps Amazon fulfill orders with unmatched accuracy. Since we began working with robotics, we've added over a million new...
Compliance Ranges Comparison

Kraken Technologies Japan







Amazon Fulfillment Technologies & Robotics






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Kraken Technologies Japan in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Amazon Fulfillment Technologies & Robotics in 2026.
Incident History - Kraken Technologies Japan (X = Date, Y = Severity)
Kraken Technologies Japan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amazon Fulfillment Technologies & Robotics (X = Date, Y = Severity)
Amazon Fulfillment Technologies & Robotics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Kraken Technologies Japan

Amazon Fulfillment Technologies & Robotics
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout