[{"data":1,"prerenderedAt":40},["ShallowReactive",2],{"sicherheitsluecke-cve-2026-124737":3},{"l":4,"details":22,"weitere":25,"indexierbar":10,"updated":39},{"cve":5,"status":6,"vendor":7,"product":8,"name":7,"added":9,"due":7,"ransomware":10,"published":9,"cwes":11,"cvss":13,"slug":18,"bereich":19,"schweregrad":20,"art":21,"produktLabel":8},"CVE-2026-124737","gemeldet","","BusyBox","2026-11-11",false,[12],"CWE-787",{"version":14,"score":15,"severity":16,"vector":17},"3.1",7.5,"HIGH","CVSS:3.1\u002FAV:N\u002FAC:H\u002FPR:N\u002FUI:R\u002FS:U\u002FC:H\u002FI:H\u002FA:H","cve-2026-124737","os","hoch","Speicherfehler (Schreiben außerhalb des erlaubten Bereichs)",{"description":23,"refs":24},"A flaw was found in BusyBox. When the TFTP (Trivial File Transfer Protocol) client requests a custom small block size and receives a standard response, it falls back to the default block size without resizing the allocated memory buffer. A malicious TFTP server can exploit this issue by sending standard-sized network packets during a transfer, causing a heap buffer overflow. This flaw allows an attacker to achieve arbitrary code execution or cause a Denial of Service (DoS) by crashing the application.",[],[26,29,31],{"cve":27,"status":6,"produktLabel":8,"vendor":7,"product":8,"art":21,"bereich":19,"schweregrad":20,"score":28,"epss":-1,"added":9,"ransomware":10},"CVE-2026-124741",7.6,{"cve":30,"status":6,"produktLabel":8,"vendor":7,"product":8,"art":21,"bereich":19,"schweregrad":20,"score":15,"epss":-1,"added":9,"ransomware":10},"CVE-2026-124739",{"cve":32,"status":6,"produktLabel":33,"vendor":34,"product":35,"art":36,"bereich":19,"schweregrad":20,"score":37,"epss":-1,"added":38,"ransomware":10},"CVE-2026-119908","Microsoft Windows Storage Spaces Controller","Microsoft","Windows Storage Spaces Controller","Zahlenunterlauf (Integer Underflow)",8.8,"2026-11-10","2026-11-11T14:28:43.107Z",1794407350181]