Comparison Overview
Médecins Sans Frontières/Doctors Without Borders (MSF) Eastern Africa

Médecins Sans Frontières/Doctors Without Borders (MSF) Eastern Africa
Jakaya Kikwete Road, Nairobi, Nairobi, 60204 - 00200, KE
Last Update: 30/01/2026
MSF medical teams work in more than 70 countries to provide lifesaving assistance where it is needed the most. In 2019, 65,000 people worked with MSF in conflicts, epidemics, following natural disasters and where people would not otherwise have access to medical care. W...

Save the Children International
1 St. Johns Lane , London, England, GB, EC1M 4BL
Last Update: 04/04/2026
Save the Children Save the Children is the world's leading independent organisation for children. We work in around 120 countries. Our vision is to live in a world in which every child attains the right to survival, protection, development and participation. Last...
Compliance Ranges Comparison

Médecins Sans Frontières/Doctors Without Borders (MSF) Eastern Africa







Save the Children International






Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for Médecins Sans Frontières/Doctors Without Borders (MSF) Eastern Africa in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for Save the Children International in 2026.
Incident History - Médecins Sans Frontières/Doctors Without Borders (MSF) Eastern Africa (X = Date, Y = Severity)
Médecins Sans Frontières/Doctors Without Borders (MSF) Eastern Africa cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Save the Children International (X = Date, Y = Severity)
Save the Children International cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Médecins Sans Frontières/Doctors Without Borders (MSF) Eastern Africa

Save the Children International
FAQ
Latest Global CVEs
Deserialization of untrusted data in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
The Bluetooth BAP Broadcast Assistant GATT client in subsys/bluetooth/audio/bap_broadcast_assistant.c reassembled remote Broadcast Receive State data into a single file-static net_buf_simple (att_buf, BT_ATT_MAX_ATTRIBUTE_LEN = 512 bytes) shared by all connection instances, while the BUSY flag, long-read handle, and reset/offset state were per-connection. When the device acts as a Broadcast Assistant connected to multiple Scan Delegator peripherals, notification and long-read callbacks from different connections interleave on the shared buffer: the append in notify_handler (net_buf_simple_add_mem at the not-busy branch) performs no tailroom check, so receive-state notifications from two or more delegators accumulate on the same 512-byte buffer and, with a sufficiently large configured ATT MTU (BT_L2CAP_TX_MTU up to 2000) and two-to-three concurrent connections, write past the buffer into adjacent .bss (net_buf_simple_add only asserts in debug builds). Even below the overflow threshold, one connection's net_buf_simple_reset zeroes the shared length while another connection's reassembly and GATT read offset are in flight, mixing one peer's data into another's parse. A malicious or compromised Scan Delegator (or two colluding peers) over BLE can trigger this, causing out-of-bounds writes (memory corruption / denial of service) and cross-connection data corruption. The fix moves the buffer into the per-connection instance struct so each connection reassembles into its own buffer. Affects Zephyr releases shipping the Broadcast Assistant with the shared buffer, including v4.4.0 and earlier.
ImageMagick before 7.1.2-26 contains a memory leak vulnerability in the VIFF encoder when memory allocation fails. Attackers can trigger allocation failures by processing specially crafted VIFF images to exhaust available memory and cause denial of service.
ImageMagick before 7.1.2-26 contains a use-after-free vulnerability in the FormatMagickCaption method when memory allocation fails. Attackers can trigger memory allocation failures to cause a dangling pointer to reference freed memory, potentially enabling denial of service or code execution.
ImageMagick before 7.1.2-26 contains a policy bypass vulnerability in the APNG encoder and external delegates due to missing validation checks. Attackers can write files to disallowed paths by bypassing configured policy restrictions through the APNG encoding process.