{"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-2026-27167 exists.","fix":"Upgrade gradio to 6.6.0 or later.","what":"CVE-2026-27167 is a vulnerability in Gradio Project Gradio, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27167 and fix it if it is affected.\n\nWhat it is: CVE-2026-27167 is a vulnerability in Gradio Project Gradio, published on 27 Feb 2026. 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-2026-27167 exists.\n\nAffected packages and fixed versions:\n- gradio (PyPI): affected from 4.16.0; fixed in 6.6.0\n- gradio (PyPI): affected from 4.16.0; fixed in 6.6.0\n- gradio (PyPI): affected from 4.16.0; fixed in 6.6.0\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-2026-27167/ (Markdown: https://insights.sbomify.com/CVE-2026-27167/index.md)","id":"CVE-2026-27167","markdown":"https://insights.sbomify.com/CVE-2026-27167/index.md","name":"CVE-2026-27167","record":{"aliases":["GHSA-h3h8-3v2v-rg7m","PYSEC-2026-63"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Python ML prototyping library","requires_auth":"none","summary":"Remote attackers can steal server Hugging Face tokens via mocked OAuth routes using a hardcoded session secret in Gradio applications.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gradio","vendor":"gradio_project"}],"cvss":{"score":0,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Gradio is an open-source Python package designed for quick prototyping. Starting in version 4.16.0 and prior to version 6.6.0, Gradio applications running outside of Hugging Face Spaces automatically enable \"mocked\" OAuth routes when OAuth components (e.g. `gr.LoginButton`) are used. When a user visits `/login/huggingface`, the server retrieves its own Hugging Face access token via `huggingface_hub.get_token()` and stores it in the visitor's session cookie. If the application is network-accessible, any remote attacker can trigger this flow to steal the server owner's HF token. The session cookie is signed with a hardcoded secret derived from the string `\"-v4\"`, making the payload trivially decodable. Version 6.6.0 fixes 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":true,"headline":"Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret","id":"CVE-2026-27167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"gradio_project:gradio","products":["gradio_project:gradio"],"type":"hardcoded_credentials","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"SAIL: Heap-based Buffer Overflow in Sail-codecs-xwd","id":"CVE-2026-27168"},"packages":[{"ecosystem":"PyPI","fixed":["6.6.0"],"introduced":["4.16.0"],"last_affected":[],"package":"gradio","purl":null,"source":"GHSA-h3h8-3v2v-rg7m"},{"ecosystem":"PyPI","fixed":["6.6.0"],"introduced":["4.16.0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"GHSA-h3h8-3v2v-rg7m"},{"ecosystem":"PyPI","fixed":["6.6.0"],"introduced":["4.16.0"],"last_affected":[],"package":"gradio","purl":"pkg:pypi/gradio","source":"PYSEC-2026-63"}],"prev":{"headline":"Discourse vulnerable to HTML injection via prohibited iframe URLs","id":"CVE-2026-27166"},"products":["gradio"],"published":"2026-02-27","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["gradio-app"]},"summary":"Remote attackers can steal server Hugging Face tokens via mocked OAuth routes using a hardcoded session secret in Gradio applications.","url":"https://insights.sbomify.com/CVE-2026-27167/"}