ray vulnerable to Insertion of Sensitive Information into Log File

Exploitation

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

CVSS 4.0

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

EPSS

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

Versions of the package ray before 2.43.0 are vulnerable to Insertion of Sensitive Information into Log File where the redis password is being logged in the standard logging. If the redis password is passed as an argument, it will be logged and could potentially leak the password. This is only exploitable if: 1) Logging is enabled; 2) Redis is using password authentication; 3) Those logs are accessible to an attacker, who can reach that redis instance. Note: It is recommended that anyone who is running in this configuration should update to the latest version of Ray, then rotate their redis password.

Published by the source

6 Mar 2025, 06:30 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 13:31 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-w4rh-fgx7-q63m

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-w4rh-fgx7-q63m

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

# Patch Next advisory brief: CVE-2025-1979

Advisory: ray vulnerable to Insertion of Sensitive Information into Log File
IDs: CVE-2025-1979, GHSA-w4rh-fgx7-q63m
Record: https://patchnext.com/advisories/cve-2025-1979 (revision 3, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ray 2.43.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI ray: affected < 2.43.0; fixed in 2.43.0

## Suggested inspection (read-only)
- `python -m pip show ray`: 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 ray.
- 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-w4rh-fgx7-q63m (OSV record GHSA-w4rh-fgx7-q63m lists affected ranges: PyPI ray >=0 <2.43.0 (fixed))
- Verified: https://github.com/advisories/GHSA-w4rh-fgx7-q63m (GitHub-reviewed advisory GHSA-w4rh-fgx7-q63m lists affected ranges: PyPI ray >=0 <2.43.0)

Commands are suggestions: review each one before running it.