{"answers":{"affected":"3 open source packages ship an affected version, including invokeai and InvokeAI.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11043 exists.","fix":"No fix has been published for CVE-2024-11043 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-11043 is a high-severity denial of service vulnerability in invoke-ai/invokeai, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-11043 and fix it if it is affected.\n\nWhat it is: CVE-2024-11043 is a high-severity denial of service vulnerability in invoke-ai/invokeai, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11043 exists.\n\nAffected packages and fixed versions:\n- invokeai (PyPI): affected all versions up to 5.0.2; no fix listed\n- invokeai (PyPI): affected all versions up to 5.0.2; no fix listed\n- InvokeAI (PyPI): affected all versions up to 5.0.2; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-11043/ (Markdown: https://insights.sbomify.com/CVE-2024-11043/index.md)","id":"CVE-2024-11043","markdown":"https://insights.sbomify.com/CVE-2024-11043/index.md","name":"CVE-2024-11043","record":{"aliases":["GHSA-ffh5-w482-c7m5","PYSEC-2026-1467"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"AI image generation tool","requires_auth":"none","summary":"Attackers can cause denial of service by sending large payloads to the board name field, making the UI unresponsive and preventing board management.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"A Denial of Service (DoS) vulnerability was discovered in the /api/v1/boards/{board_id} endpoint of invoke-ai/invokeai version v5.0.2. This vulnerability occurs when an excessively large payload is sent in the board_name field during a PATCH request. By sending a large payload, the UI becomes unresponsive, rendering it impossible for users to interact with or manage the affected board. Additionally, the option to delete the board becomes inaccessible, amplifying the severity of the issue.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Denial of Service (DoS) via Large Payload in Board Name Field in invoke-ai/invokeai","id":"CVE-2024-11043","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Open Redirect in automatic1111/stable-diffusion-webui","id":"CVE-2024-11044"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["5.0.2"],"package":"InvokeAI","purl":null,"source":"GHSA-ffh5-w482-c7m5"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["5.0.2"],"package":"invokeai","purl":"pkg:pypi/invokeai","source":"GHSA-ffh5-w482-c7m5"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["5.0.2"],"package":"invokeai","purl":"pkg:pypi/invokeai","source":"PYSEC-2026-1467"}],"prev":{"headline":"Arbitrary File Delete in invoke-ai/invokeai","id":"CVE-2024-11042"},"products":["invoke-ai/invokeai"],"published":"2025-03-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["invoke-ai"]},"summary":"Attackers can cause denial of service by sending large payloads to the board name field, making the UI unresponsive and preventing board management.","url":"https://insights.sbomify.com/CVE-2024-11043/"}