🛡️ CVE-2026-44889 — webob

🟡 CVSS 6.1 — Medium ✅ No Known Exploit CWE-601 OSV
6.1
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

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

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity low, availability none.

Weakness class

CVE-2026-44889 is classified as CWE-601: Open Redirect. A redirect target is taken from user input, so a trusted link can send the visitor to an attacker's site.

Affected software

CVE-2026-44889 is recorded against 1 package.

  • webob (fixed in 1.8.10)

Timeline and source

Published on 4 June 2026 and last revised on 18 July 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Package)
github.com (Web)
github.com (Web)

Details

Severity MEDIUM
CVSS Score 6.1
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CWE CWE-601
Public Exploit ✅ No
Source OSV
Published 2026-06-04
Updated 2026-08-12
Modified 2026-07-18
Fix URL N/A

Affected Packages

Software From version Fixed in
webob 1.8.10

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in webob

CVE-2026-44889 is rated CVSS 6.1 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.