Skip to main content
Menu
CVEs

CKAN account hijack via session fixation in registration view

CVE-2026-104773Published November 19, 2026, updated

6.8MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.10.11, 2.11.6
Who is exposed
Not reported

Summary

CKAN, an open-source data management system, has a session fixation flaw in its web user registration. A remote attacker who can set or learn a victim's session identifier can reuse it after the victim registers and gain access to the new account, but this requires the victim to take action and applies only when server-side session storage is configured.

Written by a model

Original description

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.

What to do

Upgrade to a fixed version: 2.10.11, 2.11.6.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-104773 (CKAN: Session Fixation in Registration View), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-104773 (entry last updated 2026-11-19):
Affected:
- ckan ckan: fixed in 2.10.11; from 2.11.0, fixed in 2.11.6
Fixed versions: 2.10.11, 2.11.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-104773 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104773 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ckan/ckan/security/advisories/GHSA-6499-jgj4-2wpf
- https://github.com/ckan/ckan/commit/6eae4e9c430e163b9d6cc75a3fd2ca82e79d80f6
- https://github.com/ckan/ckan/commit/8f8e8b587461b66120ec7a85c17a34ecea213f57
- https://github.com/ckan/ckan/commit/a25e2f3080a79a94eb04dcf02e16ded3e5fadeb2
- https://github.com/ckan/ckan/commit/c30bae7fdd616d98a5d47cc31f9e8d5d1ad7bcd2
- https://github.com/ckan/ckan/commit/c72815a5afd50cf689fcfb688f431dec21a85915
- https://github.com/ckan/ckan/releases/tag/ckan-2.10.11
- https://github.com/ckan/ckan/releases/tag/ckan-2.11.6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-104773
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-104773"}.

Affected versions

cve.now Index

14Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. Record last updated
  3. First seen by cve.now

Evidence 11

Questions about CVE-2026-104773

Is CVE-2026-104773 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-104773?

ckan: before 2.10.11; from 2.11.0 before 2.11.6.

Source: cve.now feed data

How do I fix CVE-2026-104773?

Upgrade to a fixed version: 2.10.11, 2.11.6.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.