{"answers":{"affected":"3 open source packages ship an affected version, including gradio. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24770 in the wild and no public exploit code.","fix":"Upgrade gradio to 2.8.11 or later.","what":"CVE-2022-24770 is a high-severity code injection vulnerability in Gradio Project Gradio, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-24770 and fix it if it is affected.\n\nWhat it is: CVE-2022-24770 is a high-severity code injection vulnerability in Gradio Project Gradio, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-24770 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gradio (PyPI): affected all versions; fixed in 2.8.11\n- gradio (PyPI): affected all versions; fixed in 2.8.11\n- gradio (PyPI): affected all versions; fixed in 2.8.11\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-2022-24770/ (Markdown: https://insights.sbomify.com/CVE-2022-24770/index.md)","id":"CVE-2022-24770","markdown":"https://insights.sbomify.com/CVE-2022-24770/index.md","name":"CVE-2022-24770","record":{"aliases":["GHSA-f8xq-q7px-wg8c","PYSEC-2022-229"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python ML framework","requires_auth":"none","summary":"Attackers can inject malicious formulas into CSV files via Gradio's flagging feature, leading to arbitrary code execution when opened in spreadsheet software.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gradio","vendor":"gradio_project"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"description":"`gradio` is an open source framework for building interactive machine learning models and demos. Prior to version 2.8.11, `gradio` suffers from Improper Neutralization of Formula Elements in a CSV File. The `gradio` library has a flagging functionality which saves input/output data into a CSV file on the developer's computer. This can allow a user to save arbitrary text into the CSV file, such as commands. If a program like MS Excel opens such a file, then it automatically runs these commands, which could lead to arbitrary commands running on the user's computer. The problem has been patched as of `2.8.11`, which escapes the saved csv with single quotes. As a workaround, avoid opening csv files generated by `gradio` with Excel or similar spreadsheet programs.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging","id":"CVE-2022-24770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"gradio_project:gradio","products":["gradio_project:gradio"],"type":"code_injection","year":"2022"},"n_packages":3,"n_references":3,"next":{"headline":"Improper Verification of Cryptographic Signature in node-forge","id":"CVE-2022-24771"},"packages":[{"ecosystem":"PyPI","fixed":["2.8.11"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":null,"source":"GHSA-f8xq-q7px-wg8c"},{"ecosystem":"PyPI","fixed":["2.8.11"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"GHSA-f8xq-q7px-wg8c"},{"ecosystem":"PyPI","fixed":["2.8.11"],"introduced":["0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"PYSEC-2022-229"}],"prev":{"headline":"Default inheritable capabilities for linux container should be empty","id":"CVE-2022-24769"},"products":["gradio"],"published":"2022-03-17","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.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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["gradio-app"]},"summary":"Attackers can inject malicious formulas into CSV files via Gradio's flagging feature, leading to arbitrary code execution when opened in spreadsheet software.","url":"https://insights.sbomify.com/CVE-2022-24770/"}