Hail relies on OIDC email claims to verify the validity of a user's domain.

Exploitation

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

CVSS

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

EPSS

• CVE-2023-51663: 0.37% estimated exploitation activity in the next 30 days; percentile 30.61 (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 All Hail Batch clusters are affected. An attacker is able to: 1. Create one or more accounts with Hail Batch without corresponding real accounts in the organization. For example, a user could create a Microsoft or Google account and then change their email to "inconspicuous@example.org". This Microsoft or Google account can then be used to create a Hail Batch account in Hail Batch clusters whose organization domain is "example.org". In Google, this attack is partially mitigated because Google requires users to verify ownership of their Google account. However, a valid user is able to create multiple distinct Hail Batch accounts by creating multiple distinct Google accounts using email addresses of the form "realuseremailname+randomid@example.org". In Microsoft, this attack requires Azure AD Administrator access to an Azure AD Tenant. The Azure AD Administrator is permitted to change the email address of an account to any other email address without verification. An attacker…

Published by the source

2 Jan 2024, 16:40 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 13:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-487p-qx68-5vjw

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-487p-qx68-5vjw

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

# Patch Next advisory brief: CVE-2023-51663

Advisory: Hail relies on OIDC email claims to verify the validity of a user's domain.
IDs: CVE-2023-51663, GHSA-487p-qx68-5vjw
Record: https://patchnext.com/advisories/cve-2023-51663 (revision 2, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hail 0.2.127. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI hail: affected < 0.2.127; fixed in 0.2.127

## Suggested inspection (read-only)
- `python -m pip show hail`: 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 hail.
- 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-487p-qx68-5vjw (OSV record GHSA-487p-qx68-5vjw lists affected ranges: PyPI hail >=0 <0.2.127 (fixed))
- Verified: https://github.com/advisories/GHSA-487p-qx68-5vjw (GitHub-reviewed advisory GHSA-487p-qx68-5vjw lists affected ranges: PyPI hail >=0 <0.2.127)

Commands are suggestions: review each one before running it.