Nixpkgs Security Tracker

Login with GitHub

Details of issue NIXPKGS-2026-0508

NIXPKGS-2026-0508
published on 3 Mar 2026
Permalink CVE-2026-27167
0.0 NONE
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): HIGH
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): NONE
  • Integrity impact (I): NONE
  • Availability impact (A): NONE
updated 2 weeks, 6 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    8 packages
    • python312Packages.gradio-pdf
    • python313Packages.gradio-pdf
    • python314Packages.gradio-pdf
    • python312Packages.gradio-client
    • python313Packages.gradio-client
    • python314Packages.gradio-client
    • pkgsRocm.python3Packages.gradio-pdf
    • pkgsRocm.python3Packages.gradio-client
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret

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.

Affected products

gradio
  • ==>= 4.16.0, < 6.6.0

Matching in nixpkgs

Ignored packages (8)

Package maintainers

Upstream advisory: https://github.com/gradio-app/gradio/security/advisories/GHSA-h3h8-3v2v-rg7m