Comparison Overview
John Crane Japan

John Crane Japan
2222 Kamitoyama, Ritto, 520-3084, JP
Last Update: 06/02/2026
世界の進歩を牽引しているプロセス産業ですが、そのプロセス産業の企業様方には、効率的な業務運営を維持するため、当社John Craneをご愛顧いただいています。当社の専門家たちは、お客様からの信頼を最大限に実現するノウハウを持ち合わせており、当社は、最新の技術を活用して、極めて重要な回転機器や課題の多い環境に対応するために必要なイノベーションを生み出しています。そして、お客様が必要としているときに、当社は迅速に応えることが可能です。また、100年にわたり重要な役割を果たしてきたJohn Craneは、グローバルな規模の産業で変化し続ける...

repsol
Méndez Álvaro, 44, Madrid, Madrid, ES, 28045
Last Update: 02/04/2026
What do you do with the energy that drives you every day? We strive to turn it into something useful for you—your decisions and your next steps. We are a company that explores multi-energy solutions through innovation, technology, and the curiosity of our team. With ove...
Compliance Ranges Comparison

John Crane Japan







repsol






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 repsol 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 - repsol (X = Date, Y = Severity)
repsol cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

John Crane Japan

repsol
FAQ
Latest Global CVEs
PlaywrightCapture stored capture-specific configuration and runtime data as mutable class-level variables rather than instance-level variables. Consequently, multiple Capture objects running within the same Python process could share state, including HTTP headers, cookies, browser storage, HTTP credentials, proxy configuration, user-agent settings, geolocation information, and captured request data. In a multi-user or concurrent deployment, information supplied during one capture could therefore persist and be reused by a subsequent or parallel capture. This could result in the disclosure of authentication cookies, credentials, browser storage, or captured request data belonging to another user. It could also cause requests to be performed with another capture's authentication context, headers, or proxy configuration, potentially enabling unauthorized access to remote resources or interference with other capture operations. The vulnerability is resolved by initializing all capture-specific settings and request data as instance variables in the Capture constructor, ensuring that state is isolated between capture operations.
Anubis is a Web AI Firewall Utility that challenges users' connections in order to protect upstream resources from scraper bots. From 1.22.0 until 1.26.0-pre1, lib/policy/checker.go PathChecker.Check() trusted the client-controlled X-Original-URI header before matching r.URL.Path, allowing an HTTP client to match default data/common/keep-internet-working.yaml ALLOW rules such as ^/\.well-known/.*$ and bypass the Anubis challenge. This issue is fixed in version 1.26.0-pre1.
Wekan is open source kanban built with Meteor. Prior to 9.46, header-login with HEADER_LOGIN_TRUSTED_IPS uses getRequestIp() in server/lib/headerLoginAuth.js to trust the client-supplied X-Forwarded-For header before the real socket address, allowing an unauthenticated attacker to send HEADER_LOGIN_ID for any username and receive a meteor_login_token session, including for admin. This issue is fixed in version 9.46.
MaaAssistantArknights is a one-click tool for daily Arknights tasks. In the current dev-v2 workflow, .github/workflows/release-preparation.yml inlined attacker-controlled github.event.pull_request.title into a run: shell command during the pull_request opened, reopened, and ready_for_review events, so a non-draft fork PR whose title starts with Release v could execute shell commands on the ubuntu-latest runner during the generate-changelog job. This vulnerability is fixed by commit cafc3946059e6337d2089d4fec8b6885ba17c332.
Qinglong is a timed task management platform supporting Python3, JavaScript, Shell, and Typescript. Prior to 2.20.1, the init guard middleware in back/loaders/express.ts checks /api/user/init but not /open/user/init, while rewrite('/open/*', '/api/$1') rewrites the whitelisted /open/* path after JWT authentication and the guard have passed; an unauthenticated attacker can send PUT /open/user/init to reset administrator credentials on an initialized instance. This issue is fixed in 2.20.1.