{"answers":{"affected":"3 open source packages ship an affected version, including gradio. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10624 exists.","fix":"No fix has been published for CVE-2024-10624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-10624 is a high-severity denial of service vulnerability in Gradio Project Gradio, 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-10624 and fix it if it is affected.\n\nWhat it is: CVE-2024-10624 is a high-severity denial of service vulnerability in Gradio Project Gradio, 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-10624 exists.\n\nAffected packages and fixed versions:\n- gradio (PyPI): affected from 4.38.0 up to 5.0.0-beta.2; no fix listed\n- gradio (PyPI): affected from 4.38.0 up to 5.0.0-beta.2; no fix listed\n- gradio (PyPI): affected from 4.38.0 up to 5.0.0-beta.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-10624/ (Markdown: https://insights.sbomify.com/CVE-2024-10624/index.md)","id":"CVE-2024-10624","markdown":"https://insights.sbomify.com/CVE-2024-10624/index.md","name":"CVE-2024-10624","record":{"aliases":["GHSA-rvgh-pr46-x7gg","PYSEC-2026-1421"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python web UI library","requires_auth":"none","summary":"Attackers can cause server CPU exhaustion and denial of service via crafted input in the gradio library's datetime component.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"gradio","vendor":"gradio_project"}],"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-1333","name":"Inefficient Regular Expression Complexity"}],"description":"A Regular Expression Denial of Service (ReDoS) vulnerability exists in the gradio-app/gradio repository, affecting the gr.Datetime component. The affected version is git commit 98cbcae. The vulnerability arises from the use of a regular expression `^(?:\\s*now\\s*(?:-\\s*(\\d+)\\s*([dmhs]))?)?\\s*$` to process user input. In Python's default regex engine, this regular expression can take polynomial time to match certain crafted inputs. An attacker can exploit this by sending a crafted HTTP request, causing the gradio process to consume 100% CPU and potentially leading to a Denial of Service (DoS) condition on the server.","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":"Regular Expression Denial of Service (ReDoS) in gradio-app/gradio","id":"CVE-2024-10624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"gradio_project:gradio","products":["gradio_project:gradio"],"type":"denial_of_service","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"WooCommerce Support Ticket System \u003c= 17.7 - Unauthenticated Arbitrary File Deletion","id":"CVE-2024-10625"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["4.38.0"],"last_affected":["5.0.0-beta.2"],"package":"gradio","purl":null,"source":"GHSA-rvgh-pr46-x7gg"},{"ecosystem":"PyPI","fixed":[],"introduced":["4.38.0"],"last_affected":["5.0.0-beta.2"],"package":"gradio","purl":"pkg:pypi/gradio","source":"GHSA-rvgh-pr46-x7gg"},{"ecosystem":"PyPI","fixed":[],"introduced":["4.38.0"],"last_affected":["5.0.0-beta.2"],"package":"gradio","purl":"pkg:pypi/gradio","source":"PYSEC-2026-1421"}],"prev":{"headline":"ForumEngine \u003c= 1.8 - Reflected Cross-Site Scripting","id":"CVE-2024-10623"},"products":["gradio-app/gradio"],"published":"2025-03-20","related":[{"cvss_score":9.8,"headline":"Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py","id":"CVE-2024-39236","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":9.6,"headline":"Command Injection in gradio-app/gradio","id":"CVE-2023-6572","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.8,"headline":"Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging","id":"CVE-2022-24770","kev_date_added":null,"published":"2022-03-17"},{"cvss_score":8.7,"headline":"Gradio \u003c 6.16.0 Path Traversal via FileExplorer.preprocess()","id":"CVE-2026-49119","kev_date_added":null,"published":"2026-07-01"},{"cvss_score":8.7,"headline":"Gradio Blocked Path ACL Bypass Vulnerability","id":"CVE-2025-23042","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8.6,"headline":"Server-Side Request Forgery (SSRF) in gradio-app/gradio","id":"CVE-2024-4325","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":8.6,"headline":"Command Injection in gradio-app/gradio via deploy+test-visual.yml workflow","id":"CVE-2024-1540","kev_date_added":null,"published":"2024-03-27"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-10-15","vendors":["gradio-app"]},"summary":"Attackers can cause server CPU exhaustion and denial of service via crafted input in the gradio library's datetime component.","url":"https://insights.sbomify.com/CVE-2024-10624/"}