Update share links to use FRP instead of SSH tunneling

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L · score source

EPSS

• CVE-2023-25823: 0.55% estimated exploitation activity in the next 30 days; percentile 46.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This is a vulnerability which affects anyone using Gradio's share links (i.e. creating a Gradio app and then setting share=True) with Gradio versions older than 3.13.1. In these older versions of Gradio, a private SSH key is sent to any user that connects to the Gradio machine, which means that a user could access other users' shared Gradio demos. From there, other exploits are possible depending on the level of access/exposure the Gradio app provides. Patches The problem has been patched. Ideally, users should upgrade to gradio==3.19.1 or later where the FRP solution has been properly tested. Credit Credit to Greg Sadetsky and Samuel Tremblay-Cossette for alerting the team

Published by the source

23 Feb 2023, 22:10 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

26 Oct 2026, 13:17 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3x5j-9vwr-8rr5

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3x5j-9vwr-8rr5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-25823

Advisory: Update share links to use FRP instead of SSH tunneling
IDs: CVE-2023-25823, GHSA-3x5j-9vwr-8rr5
Record: https://patchnext.com/advisories/cve-2023-25823 (revision 3, source checked 26 Oct 2026, 13:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gradio 3.13.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gradio: affected < 3.13.1; fixed in 3.13.1

## Suggested inspection (read-only)
- `python -m pip show gradio`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gradio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3x5j-9vwr-8rr5 (OSV record GHSA-3x5j-9vwr-8rr5 lists affected ranges: PyPI gradio >=0 <3.13.1 (fixed))
- Verified: https://github.com/advisories/GHSA-3x5j-9vwr-8rr5 (GitHub-reviewed advisory GHSA-3x5j-9vwr-8rr5 lists affected ranges: PyPI gradio >=0 <3.13.1)

Commands are suggestions: review each one before running it.