Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

SafeURL-Python's hostname blocklist does not block FQDNs

GHSA-373w-rj84-pv6x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (safeurl-python 1.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Description If a hostname was blacklisted, it was possible to bypass the blacklist by requesting the FQDN of the host (e.g. adding . to the end). Impact The main purpose of this library is to block requests to internal/private IPs and these cannot be bypassed using this finding. But if a library user had specifically set certain hostnames as blocked, then an attacker would be able to circumvent that block to cause SSRFs to request those hostnames. Patches Fixed by https://github.com/IncludeSecurity/safeurl-python/pull/6 Credit https://github.com/Sim4n6

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-373w-rj84-pv6x

  2. Revision 1 · created ·

    Published from osv record GHSA-373w-rj84-pv6x

Agent brief

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

# Patch Next advisory brief: GHSA-373w-rj84-pv6x

Advisory: SafeURL-Python's hostname blocklist does not block FQDNs
IDs: GHSA-373w-rj84-pv6x
Record: https://patchnext.com/advisories/ghsa-373w-rj84-pv6x (revision 2, source checked 26 Oct 2026, 13:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: safeurl-python 1.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI safeurl-python: affected < 1.3; fixed in 1.3

## Suggested inspection (read-only)
- `python -m pip show safeurl-python`: 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 safeurl-python.
- 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-373w-rj84-pv6x (OSV record GHSA-373w-rj84-pv6x lists affected ranges: PyPI safeurl-python >=0 <1.3 (fixed))
- Verified: https://github.com/advisories/GHSA-373w-rj84-pv6x (GitHub-reviewed advisory GHSA-373w-rj84-pv6x lists affected ranges: PyPI safeurl-python >=0 <1.3)

Commands are suggestions: review each one before running it.

Loading voting…