Skip to content

Update dependency django-allauth to v65 [SECURITY] - #2711

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/pypi-django-allauth-vulnerability
Open

Update dependency django-allauth to v65 [SECURITY]#2711
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/pypi-django-allauth-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Dec 16, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
django-allauth (changelog) ==0.55.0==65.14.1 age confidence

django-allauth does not reject access tokens for inactive users

CVE-2025-65430 / GHSA-qhmc-3mvr-f2j4

More information

Details

An issue was discovered in allauth-django before 65.13.0. IdP: marking a user as is_active=False after having handed tokens for that user while the account was still active had no effect. Fixed the access/refresh tokens are now rejected.

Severity

  • CVSS Score: 5.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


django-allauth's Okta and NetIQ implementations used a mutable identifier for authorization decisions

CVE-2025-65431 / GHSA-8m3c-c723-h4p4

More information

Details

An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead.

Severity

  • CVSS Score: 5.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


django-allauth has an open redirect vulnerability

CVE-2026-27982 / GHSA-2jpr-83rg-v67j

More information

Details

An open redirect vulnerability exists in django-allauth versions prior to 65.14.1 when SAML IdP initiated SSO is enabled (it is disabled by default), which may allow an attacker to redirect users to an arbitrary external website via a crafted URL.

Severity

  • CVSS Score: 5.1 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

allauth/django-allauth (django-allauth)

v65.14.1

Compare Source

v65.14.0

Compare Source

v65.13.1

Compare Source

v65.13.0

Compare Source

v65.12.1

Compare Source

v65.12.0

Compare Source

v65.11.2

Compare Source

v65.11.1

Compare Source

v65.11.0

Compare Source

v65.10.0

Compare Source

v65.9.0

Compare Source

v65.8.1

Compare Source

v65.8.0

Compare Source

v65.7.0

Compare Source

v65.6.0

Compare Source

v65.5.0

Compare Source

v65.4.1

Compare Source

v65.4.0

Compare Source

v65.3.1

Compare Source

v65.3.0

Compare Source

v65.2.0

Compare Source

v65.1.0

Compare Source

v65.0.2

Compare Source

v65.0.1

Compare Source

v65.0.0

Compare Source

v64.2.1

Compare Source

v64.2.0

Compare Source

v64.1.0

Compare Source

v64.0.0

Compare Source

v0.63.6

Compare Source

v0.63.5

Compare Source

v0.63.4

Compare Source

v0.63.3

Compare Source

v0.63.2

Compare Source

v0.63.1

Compare Source

v0.63.0

Compare Source

v0.62.1

Compare Source

v0.62.0

Compare Source

v0.61.1

Compare Source

v0.61.0

Compare Source

v0.60.1

Compare Source

v0.60.0

Compare Source

v0.59.0

Compare Source

v0.58.2

Compare Source

v0.58.1

Compare Source

v0.58.0

Compare Source

v0.57.2

Compare Source

v0.57.1

Compare Source

v0.57.0

Compare Source

v0.56.1

Compare Source

v0.56.0

Compare Source

v0.55.2

Compare Source

v0.55.1

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the renovate label Dec 16, 2025
@renovate
renovate Bot force-pushed the renovate/pypi-django-allauth-vulnerability branch from 249e359 to 64ad70e Compare March 6, 2026 02:05
@renovate renovate Bot changed the title chore(deps): update dependency django-allauth to v65 [security] chore(deps): update dependency django-allauth to v65 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/pypi-django-allauth-vulnerability branch March 27, 2026 01:34
@renovate renovate Bot changed the title chore(deps): update dependency django-allauth to v65 [security] - autoclosed chore(deps): update dependency django-allauth to v65 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/pypi-django-allauth-vulnerability branch 2 times, most recently from 64ad70e to bfbf518 Compare March 30, 2026 22:13
@renovate renovate Bot changed the title chore(deps): update dependency django-allauth to v65 [security] Update dependency django-allauth to v65 [SECURITY] Apr 8, 2026
@renovate renovate Bot changed the title Update dependency django-allauth to v65 [SECURITY] Update dependency django-allauth to v65 [SECURITY] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title Update dependency django-allauth to v65 [SECURITY] - autoclosed Update dependency django-allauth to v65 [SECURITY] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/pypi-django-allauth-vulnerability branch 2 times, most recently from bfbf518 to 46c7c76 Compare April 27, 2026 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants