Comparison Overview
Masoneilan Control Valves

Masoneilan Control Valves
11330 Clay Rd, Houston, 77041, US
Last Update: 04/03/2026
For well over a century Masoneilan has been synonymous with innovation, leading technology and responsiveness to market needs. With its breadth of products and services, unequaled global presence and advanced process control expertise, Masoneilan is uniquely positioned...

TechnipFMC
Hadrian House, Wincomblee Road, Newcastle Upon Tyne, NE6 3PL, GB
Last Update: 08/09/2026
TechnipFMC is a leading technology provider to the traditional and new energies industry, delivering fully integrated projects, products, and services. With our proprietary technologies and comprehensive solutions, we are transforming our clients’ project economics, h...
Compliance Ranges Comparison

Masoneilan Control Valves







TechnipFMC






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Masoneilan Control Valves in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for TechnipFMC in 2026.
Incident History - Masoneilan Control Valves (X = Date, Y = Severity)
Masoneilan Control Valves cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TechnipFMC (X = Date, Y = Severity)
TechnipFMC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Masoneilan Control Valves

TechnipFMC
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.