WebOb provides objects for HTTP requests and responses. Prior to 1.8.10, the normalization of the HTTP Location header during a redirect is vulnerable to an open redirect: WebOb joins the redirect target to the request URI using Python's urljoin, and since Python 3.10 the underlying urlsplit strips ASCII tab, carriage return, and newline characters before parsing, so a redirect target containing such characters can be reinterpreted as a protocol-relative URL whose authority is an attacker-controlled host. This bypasses the CVE-2024-42353 fix that escaped a leading double slash, allowing an attacker who influences the redirect location to send users to an arbitrary external site instead of the intended one. This vulnerability is fixed in 1.8.10.
CVE-2026-44889
This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(medium)
- EPSS
- 5.7%
- KEV
- Not listed
Published
June 4, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 23, 2026Location header normalization during redirect leads to open redirect - again · Advisory · Pylons/webob · GitHub
https://github.com/Pylons/webob/security/advisories/GHSA-fh3h-vg37-cc95Vendor Advisories for CVE-2026-44889(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| webob | 0.8 ... 1.8.9 (73 versions) | 1.8.10 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 48× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:59 UTCEG score recompute
- 2026-07-06 02:59 UTCVendor advisory
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 21:36 UTCEG score recompute
- 2026-07-03 21:36 UTCVendor advisory
- 2026-07-02 21:04 UTCEG score recompute
- 2026-07-02 21:04 UTCVendor advisory
- 2026-07-01 20:24 UTCEG score recompute
- 2026-07-01 20:24 UTCVendor advisory
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 20:05 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 10:00 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:04 UTCEG score recompute
- 2026-06-27 03:44 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 03:17 UTCEG score recompute
Show 26 moreShow fewer
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 02:57 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 02:37 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 02:17 UTCEG score recompute
- 2026-06-19 23:49 UTCEG score recompute
- 2026-06-18 21:25 UTCEG score recompute
- 2026-06-17 20:57 UTCEG score recompute
- 2026-06-16 20:38 UTCEG score recompute
- 2026-06-15 20:18 UTCEG score recompute
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 19:57 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 19:38 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 19:18 UTCEG score recompute
- 2026-06-11 18:59 UTCEG score recompute
- 2026-06-10 18:40 UTCEG score recompute
- 2026-06-09 18:21 UTCEG score recompute
- 2026-06-08 18:02 UTCEG score recompute
- 2026-06-07 16:07 UTCEG score recompute
- 2026-06-06 15:48 UTCEG score recompute
- 2026-06-05 15:29 UTCEG score recompute
- 2026-06-04 15:10 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 93%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-601
Frequently asked(5)
What is CVE-2026-44889?
When was CVE-2026-44889 disclosed?
Is CVE-2026-44889 actively exploited?
What is the CVSS score of CVE-2026-44889?
How do I remediate CVE-2026-44889?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44889
Is Your Infrastructure Affected by CVE-2026-44889?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.