GHSA-fh3h-vg37-cc95

Source

https://github.com/advisories/GHSA-fh3h-vg37-cc95

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/06/GHSA-fh3h-vg37-cc95/GHSA-fh3h-vg37-cc95.json

JSON Data

https://api.test.osv.dev/v1/vulns/GHSA-fh3h-vg37-cc95

Aliases

Downstream

CGA (6)

Published

2026-06-04T14:33:35Z

Modified

2026-07-18T17:30:23Z

Severity

6.1 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N CVSS Calculator

Summary

WebOb: Location header normalization during redirect leads to open redirect - again

Details

Impact

When WebOb normalizes the HTTP Location header to include the request hostname, it does so by parsing the URL that the user is to be redirected to with Python's urllib.parse, and joining it to the base URL. urlsplit (called internally by urljoin) however treats a // at the start of a string as a URI without a scheme, and then treats the next part as the hostname. urljoin will then use that hostname from the second part as the hostname replacing the original one from the request.

In a previous advisory https://github.com/Pylons/webob/security/advisories/GHSA-mg3v-6m49-jhp3 an attempt to fix this was made by forcing the replacement of // with /%2f, however this did not take into account that since Python 3.10 urlsplit internally strips ASCII tab, carriage return, and newline characters from the string, so /\t/attacker.com gets turned into //attacker.com and the attacker is able to bypass the changes introduced in that previous advisory, thereby bringing back the problem that was attempted to be fixed.

>>> parse.urlparse("//attacker.com/some/path")
ParseResult(scheme='', netloc='attacker.com', path='/some/path', params='', query='', fragment='')

WebOb uses urljoin to take the request URI and join the redirect location to it, so assuming the request URI is https://example.org/ and the URL to redirect to is /\t/attacker.com/some/path/:

>>> parse.urljoin("https://example.org/", "/\t/attacker.com/some/path/")
'https://attacker.com/some/path/'

Which redirects from example.org where we want the user to stay to attacker.com.

Patches

This issue has been fixed in WebOb 1.8.10.

Workarounds

Any use of the Response class that includes a location can be rewritten to make sure to always pass a full URI that includes the hostname to redirect the user to, or to validate that the redirect target starts with a scheme (e.g. http:// or https://) before assigning to Response.location.

References

https://github.com/Pylons/webob/security/advisories/GHSA-mg3v-6m49-jhp3
CVE-2024-42353

Thanks

Caleb Brown of Google

Database specific

{
    "cwe_ids": [
        "CWE-601"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-04T14:33:35Z",
    "nvd_published_at": "2026-06-22T22:16:46Z",
    "severity": "MODERATE"
}

References

Affected packages

PyPI / webob

Package

Name: webob; View open source insights on deps.dev
Purl: pkg:pypi/webob

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0 Unknown introduced version / All previous versions are affected

Fixed

1.8.10

Affected versions

0.*

0.8

0.8.1

0.8.2

0.8.3

0.8.4

0.8.5

0.9

0.9.1

0.9.2

0.9.3

0.9.4

0.9.5

0.9.6

0.9.6.1

0.9.7

0.9.7.1

0.9.8

1.*

1.0

1.0.1

1.0.2

1.0.3

1.0.4

1.0.5

1.0.6

1.0.7

1.0.8

1.1beta1

1.1b2

1.1rc1

1.1

1.1.1

1.2b1

1.2b2

1.2b3

1.2rc1

1.2

1.2.1

1.2.2

1.2.3

1.3

1.3.1

1.4

1.4.1

1.4.2

1.5.0a0

1.5.0a1

1.5.0b0

1.5.0

1.5.1

1.6.0a0

1.6.0

1.6.1

1.6.2

1.6.3

1.6.4

1.7.0rc1

1.7.0rc2

1.7.0

1.7.1

1.7.2

1.7.3

1.7.4

1.8.0rc1

1.8.0

1.8.1

1.8.2

1.8.3

1.8.4

1.8.5

1.8.6

1.8.7

1.8.8

1.8.9

Database specific

last_known_affected_version_range

"<= 1.8.9"

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/06/GHSA-fh3h-vg37-cc95/GHSA-fh3h-vg37-cc95.json"