# Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret

Advisory record · `GHSA-h3h8-3v2v-rg7m`

- **Identifiers:** `GHSA-h3h8-3v2v-rg7m` · `CVE-2026-27167` · `PYSEC-2026-63`
- **State:** Confirmed
- **Severity:** CVSS 0.0 None
- **Critical:** No
- **Weakness (CWE):** [CWE-522](https://cwe.mitre.org/data/definitions/522.html) · [CWE-798](https://cwe.mitre.org/data/definitions/798.html)
- **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 1 Mar 2026
- **Updated:** 5 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Mar 2026, 01:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gradio` (PyPI): affected `>=4.16.0, <6.6.0`; fixed in `6.6.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 0.0 None, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0051, the 44th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 1 Mar 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-h3h8-3v2v-rg7m](https://github.com/advisories/GHSA-h3h8-3v2v-rg7m)
- [OSV: GHSA-h3h8-3v2v-rg7m](https://osv.dev/vulnerability/GHSA-h3h8-3v2v-rg7m)
- <https://github.com/gradio-app/gradio/security/advisories/GHSA-h3h8-3v2v-rg7m>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-27167>
- <https://github.com/gradio-app/gradio/commit/dfee0da06d0aa94b3c2684131e7898d5d5c1911e>
- <https://github.com/gradio-app/gradio>
- <https://github.com/gradio-app/gradio/releases/tag/gradio@6.6.0>
- <https://github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2026-63.yaml>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h3h8-3v2v-rg7m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h3h8-3v2v-rg7m/>. Everything for agents: <https://agentprime.io/llms.txt>.