CKAN is an open-source data management system for data hubs and data portals. Prior to 2.10.11 and 2.11.6, the web user registration flow authenticates a newly registered account without first regenerating the session identifier when server-side session storage is configured. An attacker who can set a session cookie in a victim's browser or obtain the victim's current valid session identifier can reuse that identifier after the victim registers, gaining access to the new account. CKAN uses cookie-based sessions by default, and web registration is disabled by default through ckan.auth.create_user_via_web. This issue is fixed in CKAN 2.10.11, 2.11.6, and 2.12.0.
CVE-2026-104773
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.8 from GitHub Security Advisory (severity: MODERATE) published 2026-11-20. A secondary CVSS source baseline 6.8; sources differ by 0.0.
Also known asEUVD-2026-130720 (ENISA EUVD) · GHSA-6499-jgj4-2wpf (GitHub Security Advisories)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.8
- EG Score
- 6.8MEDIUMhigh confidence
- EG Risk
- 31EG Risk 31/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity68% × 45%Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.3%
- EPSS %ILE
- 26th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
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 none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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
November 19, 2026
Last Modified
November 20, 2026
Advisory Details (9)
Auto-updated Nov 19, 2026ckan-2.12.0
Patch available: ckan/ckan ckan-2.12.0
https://github.com/ckan/ckan/releases/tag/ckan-2.12.0ckan-2.11.6
Patch available: ckan/ckan ckan-2.11.6
https://github.com/ckan/ckan/releases/tag/ckan-2.11.6ckan-2.10.11
Patch available: ckan/ckan ckan-2.10.11
https://github.com/ckan/ckan/releases/tag/ckan-2.10.11commit c72815a5afd5 (ckan/ckan)
Patch available: ckan/ckan ckan-2.11.6 (contains commit c72815a5afd5)
https://github.com/ckan/ckan/commit/c72815a5afd50cf689fcfb688f431dec21a85915commit c30bae7fdd61 (ckan/ckan)
Fix landed in ckan/ckan commit c30bae7fdd61 — awaiting tagged release
https://github.com/ckan/ckan/commit/c30bae7fdd616d98a5d47cc31f9e8d5d1ad7bcd2commit a25e2f3080a7 (ckan/ckan)
Patch available: ckan/ckan ckan-2.12.0 (contains commit a25e2f3080a7)
https://github.com/ckan/ckan/commit/a25e2f3080a79a94eb04dcf02e16ded3e5fadeb2commit 8f8e8b587461 (ckan/ckan)
Fix landed in ckan/ckan commit 8f8e8b587461 — awaiting tagged release
https://github.com/ckan/ckan/commit/8f8e8b587461b66120ec7a85c17a34ecea213f57commit 6eae4e9c430e (ckan/ckan)
Patch available: ckan/ckan ckan-2.10.11 (contains commit 6eae4e9c430e)
https://github.com/ckan/ckan/commit/6eae4e9c430e163b9d6cc75a3fd2ca82e79d80f6Session Fixation in Registration View · Advisory · ckan/ckan · GitHub
https://github.com/ckan/ckan/security/advisories/GHSA-6499-jgj4-2wpfVendor Advisories for CVE-2026-104773(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | ckan @ 2.11.6 (fixes >= 2.11.0, < 2.11.6) | — | ghsa |
| pip | ckan @ 2.10.11 (fixes < 2.10.11) | — | ghsa |
These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| ckan | 0.11 ... 2.9.9 (116 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-20 17:21 UTCEchelonGraph re-scored
- 2026-11-20 17:21 UTCGHSA enrichmentGHSA-6499-jgj4-2wpf · GitHub severity MODERATE · GitHub CVSS 6.8
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 26th percentile
- 2026-11-19 22:03 UTCENISA EUVD ID recordedEUVD-2026-130720 · Source: ENISA EUVD
- 2026-11-19 21:29 UTCEchelonGraph re-scored
- 2026-11-19 20:39 UTCEchelonGraph re-scoredFirst assessed: 6.8 MEDIUM
- 2026-11-19 20:37 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:ckan
Frequently asked(5)
What is CVE-2026-104773?
When was the CVE record for CVE-2026-104773 published?
Is CVE-2026-104773 actively exploited?
What is the CVSS score of CVE-2026-104773?
How do I remediate CVE-2026-104773?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-104773
Is Your Infrastructure Affected by CVE-2026-104773?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.