Comparison Overview
Canadian Natural Resources Limited (CNRL)

Canadian Natural Resources Limited (CNRL)
400 4 Ave SW, Calgary, T2P 0J4, CA
Last Update: 07/10/2026
MAKE YOUR MARK WHILE YOU GROW YOUR CAREER At Canadian Natural we believe our employees are the key to unlocking asset potential. As one of the largest independent crude oil and natural gas producers in the world, our balanced mix of natural gas, light oil, heavy oil, in...

PETRONAS
Kuala Lumpur, 50088, MY
Last Update: 07/09/2026
Petroliam Nasional Berhad (PETRONAS) is a leading global energy company committed to powering society’s progress in a responsible and sustainable manner. With close to 50,000 employees and a global reach spanning over 100 countries, we are ranked among the world’s large...
Compliance Ranges Comparison

Canadian Natural Resources Limited (CNRL)







PETRONAS






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

Canadian Natural Resources Limited (CNRL)

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