● None · CVSS 0

How to Fix CVE-2026-27167: Hardcoded credentials in gradio

Q: What is the CVSS score for CVE-2026-27167?

0 (None). Vector: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N`.

Q: Where is the official advisory for CVE-2026-27167?

The vendor advisory is at [https://github.com/gradio-app/gradio/security/advisories/GHSA-h3h8-3v2v-rg7m](https://github.com/gradio-app/gradio/security/advisories/GHSA-h3h8-3v2v-rg7m). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27167.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27167 is a hardcoded credentials in gradio-app gradio. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	0 (None)
Actively exploited?	No public listing in CISA KEV
Affected	gradio >= 4.16.0, < 6.6.0
Fixed in	See vendor advisory
Type (CWE)	CWE-798: Use of Hard-coded Credentials

What is CVE-2026-27167?

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. The CVSS base score is 0 (None). The official advisory is at https://github.com/gradio-app/gradio/security/advisories/GHSA-h3h8-3v2v-rg7m.

Am I affected?

Check the version of gradio you are running and compare it against the Affected row above (gradio >= 4.16.0, < 6.6.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s gradio 2>/dev/null | grep -i ^Version
rpm -q gradio 2>/dev/null
command -v gradio >/dev/null && gradio --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*gradio*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "gradio" 2>$null

How to fix CVE-2026-27167

Upgrade gradio to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade gradio
dpkg -s gradio | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh gradio -y
# or for older releases:
sudo yum update gradio -y
rpm -q gradio

SUSE / openSUSE


sudo zypper refresh
sudo zypper update gradio
rpm -q gradio

Node.js / npm


# Update the affected package in your project
npm install gradio@latest
npm ls gradio
npm audit fix

Python / pip


pip install --upgrade gradio
pip show gradio | grep -i version

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-27167 affecting gradio
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27167-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*gradio*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\gradio-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\gradio" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "gradio" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "gradio"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-27167 affecting gradio
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27167-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s gradio 2>/dev/null | grep -i ^Version || echo "gradio not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q gradio || echo "gradio not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27167-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/gradio /etc/gradio.d /etc/gradio.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y gradio
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y gradio
elif command -v yum >/dev/null; then
    yum update -y gradio
elif command -v zypper >/dev/null; then
    zypper --non-interactive update gradio
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s gradio 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q gradio
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-27167" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27167"

Disable the affected service (Linux)


sudo systemctl stop gradio 2>/dev/null || true
sudo systemctl disable gradio 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s gradio 2>/dev/null | grep -i ^Version
rpm -q gradio 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*gradio*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-3997: Critical Vulnerability in Text Toggle — Critical Vulnerability in Text Toggle
How to Fix CVE-2026-40520: OS command injection in api — OS command injection in api
How to Fix CVE-2026-2345: Critical Vulnerability in Secure Exam Proctor Extension , Critical Vulnerability in Secure Exam Proctor Extension
How to Fix CVE-2026-34889: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') , Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
How to Fix CVE-2026-44661: SSRF Vulnerability in python-utcp , SSRF Vulnerability in python-utcp

Is CVE-2026-27167 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27167?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-27167?

0 (None). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N.

Where is the official advisory for CVE-2026-27167?

The vendor advisory is at https://github.com/gradio-app/gradio/security/advisories/GHSA-h3h8-3v2v-rg7m. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27167.

References

Official vendor advisory: https://github.com/gradio-app/gradio/security/advisories/GHSA-h3h8-3v2v-rg7m
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27167
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*