Comparison Overview
AMETEK MRO Antavia

AMETEK MRO Antavia
ZAC Grand Sud Logistique , Campsas, 82370, FR
Last Update: 01/12/2025
AMETEK MRO ANTAVIA is more than your PART145 MRO provider, we aim to become your trusted partner by staying close to our customer and understand your needs: that’s how we define our global strategic network. We place the flexibility and responsiveness of a human-size co...

Blue Origin
Kent, US
Last Update: 13/09/2026
We are building a road to space for the benefit of Earth, humanity’s blue origin. Our team is focused on radically reducing the cost of access to space and harnessing its vast resources while mobilizing future generations to realize this mission. Blue Origin builds reus...
Compliance Ranges Comparison

AMETEK MRO Antavia







Blue Origin






Benchmark & Cyber Underwriting Signals
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for AMETEK MRO Antavia in 2026.
Incidents vs Aviation and Aerospace Component Manufacturing Industry Avg (This Year)
No incidents recorded for Blue Origin in 2026.
Incident History - AMETEK MRO Antavia (X = Date, Y = Severity)
AMETEK MRO Antavia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Blue Origin (X = Date, Y = Severity)
Blue Origin cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

AMETEK MRO Antavia

Blue Origin
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.