Secret theft via privileged fork code execution
Published Jun 4, 2024 · Updated Oct 21, 2025
Improper authorization in Gradio's deploy-website.yml workflow on the main branch allows remote attackers to exfiltrate repository secrets. The workflow checks out and executes attacker-controlled fork code in a privileged job that exposes repository and deployment credentials. Exploitation requires a privileged workflow run against the fork; stolen credentials expose deployment secrets and permit base-repository changes.
Summary
What happened
Improper authorization in Gradio's deploy-website.yml workflow on the main branch allows remote attackers to exfiltrate repository secrets. The workflow checks out and executes attacker-controlled fork code in a privileged job that exposes repository and deployment credentials. Exploitation requires a privileged workflow run against the fork; stolen credentials expose deployment secrets and permit base-repository changes.
The record
- CVE
- CVE-2024-4254
- Published
- Jun 4, 2024
- Updated
- Oct 21, 2025
- Vendor
- Gradio
- Product
- Gradio
- Classifications
- CWE-214, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 4, 2024CVE publishedPublication date reported by the CVE source.
- Oct 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=*
- Affected versionversion=unspecified <=latest
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo