https://vulnerability.circl.lu/sightings/feed 2026-05-11T22:25:55.677254+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/b988901a-f918-48bc-8939-1dd08a754d17/export 2026-05-11T22:25:56.068331+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "b988901a-f918-48bc-8939-1dd08a754d17", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-43366", "type": "seen", "source": "https://t.me/cvedetector/3291", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-43366 - Zkvyper Vyper Compiler Turing-Incompleteness Loop Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-43366 \nPublished : Aug. 15, 2024, 9:15 p.m. | 36\u00a0minutes ago \nDescription : zkvyper is a Vyper compiler. Starting in version 1.3.12 and prior to version 1.5.3, since LLL IR has no Turing-incompletness restrictions, it is compiled to a loop with a much more late exit condition. It leads to a loss of funds or other unwanted behavior if the loop body contains it. However, more real-life use cases like iterating over an array are not affected. No contracts were affected by this issue, which was fixed in version 1.5.3. Upgrading and redeploying affected contracts is the only way to avoid the vulnerability. \nSeverity: 7.5 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"15 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-16T00:20:23.000000Z"} 2024-08-16T00:20:23+00:00