reflex-dev/reflex has an Open Redirect vulnerability

Exploitation

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

CVSS

3.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

EPSS

• CVE-2025-62379: 0.26% estimated exploitation activity in the next 30 days; percentile 17.19 (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.

Mitigation Make sure GITHUBCODESPACESPORTFORWARDINGDOMAIN is not set in a production environment. So the following is correct: Vulnerability Description --- Vulnerability Overview - When the GET /auth-codespace page loads in a GitHub Codespaces environment, it automatically assigns the redirectto query parameter value directly to client-side links without any validation and triggers automatic clicks. This allows attackers to redirect users to arbitrary external URLs. - The route is only registered when a Codespaces environment is detected, and the detection is controlled by environment variables. This means that the same behavior can be activated in production if the corresponding environment variable is set. Vulnerable Code Analysis https://github.com/reflex-dev/reflex/blob/51f9f2c2f52cac4d66c07683a12bc0237311b6be/reflex/utils/codespaces.py#L18-L46 - This code assigns the redirectto query parameter directly to a.href without any validation and immediately triggers a click (automatic…

Published by the source

15 Oct 2025, 17:56 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:35 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rfh5-c9h5-q8jm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rfh5-c9h5-q8jm

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

# Patch Next advisory brief: CVE-2025-62379

Advisory: reflex-dev/reflex has an Open Redirect vulnerability
IDs: CVE-2025-62379, GHSA-rfh5-c9h5-q8jm
Record: https://patchnext.com/advisories/cve-2025-62379 (revision 2, source checked 26 Oct 2026, 13:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI reflex: affected >= 0.5.4, <= 0.8.14

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on reflex.
- 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-rfh5-c9h5-q8jm (OSV record GHSA-rfh5-c9h5-q8jm lists affected ranges: PyPI reflex >=0.5.4 <=0.8.14)
- Verified: https://github.com/advisories/GHSA-rfh5-c9h5-q8jm (GitHub-reviewed advisory GHSA-rfh5-c9h5-q8jm lists affected ranges: PyPI reflex >=0.5.4 <=0.8.14)

Commands are suggestions: review each one before running it.