WebOb provides objects for HTTP requests and responses. Prior to 1.8.11, Response._make_location_absolute() in src/webob/response.py checks a Location value for a URI scheme or leading double slash before urllib.parse.urljoin() strips leading C0 control characters and spaces. An attacker-controlled value such as a space followed by a protocol-relative or absolute URL can therefore bypass SCHEME_RE and startswith("//") checks and be normalized to an off-host redirect. Request.relative_url() and webob.exc._HTTPMove subclasses, including HTTPFound, are also affected because they use the same unsafe URL joining behavior or bypass the earlier normalization path. An unauthenticated attacker who can influence an application's redirect target can send users to an attacker-controlled host for phishing or OAuth and SSO token theft, but exploitation requires the user to follow the redirect. This issue is fixed in version 1.8.11.
CVE-2026-54770
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 6.1
- EG Score
- 6.1MEDIUMmedium confidence
- EG Risk
- 43EG Risk 43/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity61% × 45%The EG Score, 6.1 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 34th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
August 20, 2026
Last Modified
September 18, 2026
Advisory Details (3)
Auto-updated Aug 20, 2026commit ff89560643fb (Pylons/webob)
Fix landed in Pylons/webob commit ff89560643fb — awaiting tagged release
https://github.com/Pylons/webob/commit/ff89560643fb252751b4db8806a283b5377f1f07Open redirect in Location header normalization via leading C0 control / space characters -- third times a charm? · Advisory · Pylons/webob · GitHub
https://github.com/Pylons/webob/security/advisories/GHSA-6hx8-3wjj-gr8gVendor Advisories for CVE-2026-54770(7)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:79546Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.12.23
- RHSA-2026:79366Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.10.27
- RHSA-2026:77656Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.9.27
- RHSA-2026:74511Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.17.5
- RHSA-2026:69255Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.16.6
- GHSA-6hx8-3wjj-gr8gGitHub Security AdvisoriesMedium
WebOb: Open redirect in Location header normalization via leading C0 control / space characters
- CVE-2026-54770Microsoft Security Response Center (MSRC)Medium
WebOb: Open redirect in Location header normalization via leading C0 control / space characters
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | quay/quay-rhel9:1790690298 | 2026-10-01 | redhat |
| redhat | quay/quay-rhel9:1789563753 | 2026-09-21 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-webob | 1:1.8.10-1 ... 1:1.8.9-2 (8 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-webob | 1:1.8.10-0+deb13u1, 1:1.8.10-1, 1:1.8.11-1, 1:1.8.9-1, 1:1.8.9-2 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| python-webob | 1:1.8.10-1, 1:1.8.9-1, 1:1.8.9-2 |
| — |
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| webob | 0.8 ... 1.8.9 (74 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 66× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 99 of 108 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 9 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-12 15:56 UTCEG score recompute
- 2026-10-11 19:39 UTCEG score recompute
- 2026-10-11 16:54 UTCEG score recompute
- 2026-10-11 14:17 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-08 06:06 UTCEG score recompute
- 2026-10-08 06:06 UTCVendor advisory
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-07 04:47 UTCEG score recompute
- 2026-10-07 04:47 UTCVendor advisory
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-06 03:27 UTCEG score recompute
- 2026-10-06 03:27 UTCVendor advisory
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-04 20:52 UTCVendor advisory
- 2026-10-03 16:47 UTCEG score recompute
- 2026-10-03 16:47 UTCVendor advisory
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 74 moreShow fewer
- 2026-10-02 11:05 UTCEG score recompute
- 2026-10-02 11:05 UTCVendor advisory
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-01 09:30 UTCEG score recompute
- 2026-10-01 09:30 UTCVendor advisory
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-09-30 08:14 UTCEG score recompute
- 2026-09-30 08:14 UTCVendor advisory
- 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-29 05:37 UTCEG score recompute
- 2026-09-29 05:37 UTCVendor advisory
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-28 04:20 UTCEG score recompute
- 2026-09-28 04:20 UTCVendor advisory
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-27 03:03 UTCEG score recompute
- 2026-09-27 03:03 UTCVendor advisory
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-25 04:02 UTCEG score recompute
- 2026-09-25 04:02 UTCVendor advisory
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
- 2026-09-24 02:45 UTCEG score recompute
- 2026-09-24 02:45 UTCVendor advisory
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-23 01:29 UTCEG score recompute
- 2026-09-23 01:29 UTCVendor advisory
- 2026-09-22 00:12 UTCEG score recompute
- 2026-09-22 00:12 UTCVendor advisory
- 2026-09-20 22:53 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-19 21:36 UTCEG score recompute
- 2026-09-18 20:20 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-18 13:30 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-17 12:13 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-16 10:53 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-15 09:36 UTCEG score recompute
- 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-14 08:19 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
- 2026-09-13 07:03 UTCEG score recompute
- 2026-09-12 05:47 UTCEG score recompute
- 2026-09-11 04:30 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-09 01:57 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-07 15:33 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-06 11:50 UTCEG score recompute
- 2026-09-05 10:33 UTCEG score recompute
- 2026-09-04 09:16 UTCEG score recompute
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-03 07:59 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-02 06:34 UTCEG score recompute
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-09-01 05:18 UTCEG score recompute
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-31 04:02 UTCEG score recompute
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-30 02:45 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-29 01:28 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-27 19:11 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-26 17:53 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-08-25 15:23 UTCEG score recompute
- 2026-08-25 15:16 UTCEG score recompute
Related CVEs(same product + same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2026:69255
Frequently asked(5)
What is CVE-2026-54770?
When was the CVE record for CVE-2026-54770 published?
Is CVE-2026-54770 actively exploited?
What is the CVSS score of CVE-2026-54770?
How do I remediate CVE-2026-54770?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54770
Is Your Infrastructure Affected by CVE-2026-54770?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.