Comparison Overview
GIZ Kenya

GIZ Kenya
Nairobi, KE
Last Update: 13/03/2026
On behalf of the German Government, the Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH works with national, international and private sector partners in Kenya. Our main commissioning party is the German Federal Ministry for Economic Cooperation and D...

Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH
Friedrich-Ebert-Allee 32+36, Bonn, 53113, DE
Last Update: 14/09/2026
As a service provider in the field of international cooperation for sustainable development and international education work, we are dedicated to shaping a future worth living around the world. GIZ has over 50 years of experience in a wide variety of areas, including ec...
Compliance Ranges Comparison

GIZ Kenya







Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH






Benchmark & Cyber Underwriting Signals
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for GIZ Kenya in 2026.
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH in 2026.
Incident History - GIZ Kenya (X = Date, Y = Severity)
GIZ Kenya cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH (X = Date, Y = Severity)
Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

GIZ Kenya

Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ) GmbH
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.