Comparison Overview
Pioneer Seed South Africa

Pioneer Seed South Africa
272 West Street, Lakefield office park, 2nd floor block A, Pretoria, ZA
Last Update: 31/03/2026
We are an international company with a unique combination of cultures, languages and experiences. Our technologies and business environment have changed dramatically since Pioneer® Hi-Bred was established in 1926. Our Philosophy – Our attitude towards research, product...

Yara International
Drammensveien 131, Oslo, NO, N-0277
Last Update: 07/09/2026
Yara's mission is to responsibly feed the world and protect the planet. We pursue a strategy of sustainable value growth through reducing emissions from crop nutrition production and developing low-emission energy solutions. Yara’s ambition is focused on growing a natur...
Compliance Ranges Comparison

Pioneer Seed South Africa







Yara International






Benchmark & Cyber Underwriting Signals
Incidents vs Farming Industry Avg (This Year)
No incidents recorded for Pioneer Seed South Africa in 2026.
Incidents vs Farming Industry Avg (This Year)
No incidents recorded for Yara International in 2026.
Incident History - Pioneer Seed South Africa (X = Date, Y = Severity)
Pioneer Seed South Africa cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Yara International (X = Date, Y = Severity)
Yara International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Pioneer Seed South Africa

Yara International
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.