Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 3 min read

CVE-2026-104773: CVE-2026-104773: Session Fixation in CKAN User Registration View

CVE-2026-104773: Session Fixation in CKAN User Registration View Vulnerability ID: CVE-2026-104773 CVSS Score: 6.8 Published: 2026-11-20 A session fixation vulnerability (CWE-384) exists in CKAN (Comprehensive Knowl

CVE-2026-104773: Session Fixation in CKAN User Registration View

Vulnerability ID: CVE-2026-104773
CVSS Score: 6.8
Published: 2026-11-20

A session fixation vulnerability (CWE-384) exists in CKAN (Comprehensive Knowledge Archive Network) prior to versions 2.10.11 and 2.11.6. When configured with server-side session storage and active public web registration, the user registration view programmatically authenticates newly created accounts without regenerating the active session identifier. An attacker capable of fixing or capturing a victim's pre-authentication session cookie can hijack the newly registered account immediately after registration completes.

TL;DR

CKAN fails to regenerate session identifiers during automatic authentication after user registration when using server-side session storage. Upgrading to CKAN 2.10.11, 2.11.6, or 2.12.0 resolves the issue by forcing session regeneration prior to login.

Technical Details

  • CWE Classification: CWE-384: Session Fixation
  • CVSS v3.1 Score: 6.8 Medium (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N)
  • EPSS Score: 0.33% (26.49th Percentile)
  • Affected Component: ckan/views/user.py (Registration POST Handler)
  • Prerequisites: Server-side sessions enabled + ckan.auth.create_user_via_web = True
  • Security Impact: Account Takeover of newly registered user sessions
  • Exploit Status: None (No public weaponized exploits)
  • CISA KEV Status: Not Listed

Affected Systems

  • CKAN < 2.10.11
  • CKAN >= 2.11.0, < 2.11.6
  • CKAN: < 2.10.11 (Fixed in: 2.10.11)
  • CKAN: >= 2.11.0, < 2.11.6 (Fixed in: 2.11.6)

Code Analysis

Commit: 6eae4e9

Regenerate session in user registration view before logging in newly created user

File: ckan/views/user.py
@@ -475,6 +475,7 @@ def post(self) -> Union[Response, str]:
         # log the user in programmatically
         userobj = model.User.get(user_dict["id"])
         if userobj:
+            regenerate_session()
             login_user(userobj)
             rotate_token()
         resp = h.redirect_to(u'user.me')
@@ -548,9 +549,7 @@ def login() -> Union[Response, str]:
         user_obj = authenticator.ckan_authenticator(identity)
         if user_obj:
             next = request.args.get('next', request.args.get('came_from'))
-            regenerate = getattr(current_app.session_interface, 'regenerate', None)
-            if regenerate is not None:
-                regenerate(session)
+            regenerate_session()
             if _remember:
                 from datetime import timedelta
                 duration_time = timedelta(milliseconds=int(_remember))
@@ -572,6 +571,12 @@ def login() -> Union[Response, str]:
     return base.render("user/login.html", extra_vars)


+def regenerate_session() -> None:
+    regenerate = getattr(current_app.session_interface, 'regenerate', None)
+    if regenerate is not None:
+        regenerate(session)
+
+
 def logout() -> Response:
     for item in plugins.PluginImplementations(plugins.IAuthenticator):
         response = item.logout()

Commit: 8f8e8b5

Backport session regeneration fix for user registration view

Commit: a25e2f3

Session fixation remediation commit for CKAN release branch

Commit: c30bae7

Session fixation remediation commit for CKAN release branch

Commit: c72815a

Session fixation remediation commit for CKAN release branch

Mitigation Strategies

  • Upgrade CKAN to a patched version (2.10.11, 2.11.6, or 2.12.0) to enforce session ID rotation upon account registration.
  • Disable public self-service web registration if not operationally required by setting ckan.auth.create_user_via_web = False.
  • Use CKAN's default signed client-side cookie session storage instead of server-side session storage where feasible.
  • Harden session cookie attributes (Secure, HttpOnly, SameSite=Lax) and deploy HSTS with includeSubDomains to prevent cookie tossing and cleartext interception.

Remediation Steps:

  1. Identify whether the CKAN deployment has ckan.auth.create_user_via_web = True enabled in ckan.ini and utilizes a server-side session interface.
  2. Back up the CKAN configuration files and PostgreSQL database.
  3. Upgrade the CKAN package to version 2.10.11 (for 2.10.x deployments), 2.11.6 (for 2.11.x deployments), or 2.12.0+.
  4. Restart the CKAN WSGI application server (e.g., uWSGI or Gunicorn) and flush active server-side session stores (e.g., Redis) to invalidate any pre-existing sessions.
  5. Verify the patch by capturing HTTP response headers during a test user registration and confirming that the session identifier rotates upon POST /user/register.

References

Read the full report for CVE-2026-104773 on our website for more details including interactive diagrams and full exploit analysis.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.