---
id: CVE-2026-100169
title: >-
  Improper Authentication in the social account linking path of the Prowler API
  in Prowler from 5.4.0 before 5.35.0 allows a remote unauthenticated attacker
  to obtain persistent access to the account of a user who has not yet
  registered, b…
summary: >-
  Improper Authentication in the social account linking path of the Prowler API
  in Prowler from 5.4.0 before 5.35.0 allows a remote unauthenticated attacker
  to obtain persistent access to the account of a user who has not yet
  registered, b…
severity: none
cwe:
  - CWE-287
published: '2026-10-14'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T16:17:28.350'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-100169'
references:
  - url: >-
      https://github.com/prowler-cloud/prowler/commit/0f31f1a3c2daa05b4d77a78f451e3fbfb3fe3411
    label: 4daa8cea-433a-44bd-9456-53b127fc289a
  - url: 'https://github.com/prowler-cloud/prowler/pull/12013'
    label: 4daa8cea-433a-44bd-9456-53b127fc289a
  - url: 'https://github.com/prowler-cloud/prowler/releases/tag/5.35.0'
    label: 4daa8cea-433a-44bd-9456-53b127fc289a
  - url: >-
      https://github.com/prowler-cloud/prowler/security/advisories/GHSA-h8m9-jgf8-vwvp
    label: 4daa8cea-433a-44bd-9456-53b127fc289a
  - url: >-
      https://secur0.com/en/cna/cve-list/cve-2026-100169-prowler-account-pre-hijacking
    label: 4daa8cea-433a-44bd-9456-53b127fc289a
tags:
  - nvd
ingestedAt: '2026-10-14T16:40:32.109Z'
---

## Overview

Improper Authentication in the social account linking path of the Prowler API in Prowler from 5.4.0 before 5.35.0 allows a remote unauthenticated attacker to obtain persistent access to the account of a user who has not yet registered, because ProwlerSocialAccountAdapter.pre_social_login() in api/src/backend/api/adapters.py links a Google or GitHub login to any existing local account that has the same email address as the one returned by the provider, without requiring that the address has been verified by the provider or on the existing account, and without any other check that both accounts belong to the same person. Self registration is open and the new account is usable at once, because UserViewSet.get_permissions() in api/src/backend/api/v1/views.py grants AllowAny to the create action, ACCOUNT_EMAIL_VERIFICATION is set to none in api/src/backend/config/settings/social_login.py, and the Django ModelBackend checks only the password and is_active, not the django-allauth EmailAddress record. An attacker who registers an email address before its owner keeps the password set at registration after the link is made, because sociallogin.connect() does not reset the password and does not disable the existing account, and the owner who later signs in with Google or GitHub is logged into the attacker's account. django-allauth makes the same email based link on its own, because SOCIALACCOUNT_EMAIL_AUTHENTICATION and SOCIALACCOUNT_EMAIL_AUTHENTICATION_AUTO_CONNECT are both set to True in the same settings module. This gives the attacker the cloud provider credentials, scan findings and tenant memberships held in the account.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.