Bump social-auth-app-django from 2.1.0 to 5.6.0

[dependabot]

Bumps social-auth-app-django from 2.1.0 to 5.6.0.

Release notes

Sourced from social-auth-app-django's releases.

5.6.0

Changed

• Fixed possibly unsafe account association (CVE-2025-61783)
• Storage now filters for active users

Added

• Django 6.0 and Python 3.14 compatibility
• Type annotations
• LoginRequiredMiddleware compatibility
• RAISE_EXCEPTIONS and LOGIN_ERROR_URL can be configured per backend

Release 5.5.1

Changed

• Fixed authentication with OpenID based services

Donations

This project welcomes donations to make the development sustainable, you can fund Python Social Auth on the following platforms:

• GitHub Sponsors
• Open Collective

Release 5.5.0

Changed

• Dropped support for older Django versions.
• Added non-empty constraint on uid.
• Added support for session restore with stricter SameSite cookie policy.

Donations

This project welcomes donations to make the development sustainable, you can fund Python Social Auth on the following platforms:

• GitHub Sponsors
• Open Collective

Release 5.4.3

What's Changed

• deps: Update supported Python versions by @​a-grealish in python-social-auth/social-app-django#621
• Fixed rollback of extra_data migration by @​niklas-scholz in python-social-auth/social-app-django#626
• Modernize the build by @​offbyone in python-social-auth/social-app-django#641
• fix(ci): test django main only on Python 3.12+ by @​nijel in python-social-auth/social-app-django#647
• chore: test against Django 5.1 and 5.2 by @​nijel in python-social-auth/social-app-django#656
• chore: remove requirements files by @​nijel in python-social-auth/social-app-django#657
• chore: update tox envlist by @​nijel in python-social-auth/social-app-django#658
• chore: Version bump 5.4.3 by @​nijel in python-social-auth/social-app-django#659

... (truncated)

Changelog

Sourced from social-auth-app-django's changelog.

5.6.0 - 2025-10-09

Changed

• Fixed possibly unsafe account association (CVE-2025-61783)
• Storage now filters for active users

Added

• Django 6.0 and Python 3.14 compatibility
• Type annotations
• LoginRequiredMiddleware compatibility
• RAISE_EXCEPTIONS and LOGIN_ERROR_URL can be configured per backend

5.5.1 - 2025-06-27

Changed

• Fixed authentication with OpenID based services

5.5.0 - 2025-06-27

Changed

• Dropped support for older Django versions.
• Added non-empty constraind on uid.
• Added support for session restore with stricter SameSite cookie policy.

5.4.3 - 2025-02-13

Changed

• Tested with recent Django and Python
• Modernized build system
• Fixed rollback of migrations

5.4.2 - 2024-07-12

Changed

• Fixed UserSocialAuth creation by allowing JSONField to be blank
• Fixed the assumption that UID can only be an integer (#571)
• Fixed revert of migration 0013_migrate_extra_data.py

5.4.1 - 2024-04-24

Changed

• Added reverse migration for JSON field
• Fixed improper handling of case sensitivity with MySQL/MariaDB (CVE-2024-32879)

... (truncated)

Commits

• d1256b8 chore: release 5.6.0
• ad7154f feat: test with Python 3.14 and Django 6.0
• b0cacdb fix(deps): update dependency django-stubs to v5.2.7 (#817)
• b38830b fix(deps): update dependency django-stubs-ext to v5.2.7 (#818)
• 598056e chore(deps): update github/codeql-action action to v4 (#816)
• 6b6cf28 chore(deps): update astral-sh/setup-uv action to v7 (#815)
• 08285a3 chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.14.0 (#814)
• 1406696 chore(deps): update github/codeql-action action to v3.30.7 (#813)
• 2432af5 feat: allow to override RAISE_EXCEPTIONS and LOGIN_ERROR_URL per backend (#812)
• 47dd0a9 Fix linting issues in storage integration tests
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	sha.js@​2.4.11
	underscore@​1.9.1
	pbkdf2@​3.0.17
	socket.io-parser@​2.3.1
	xmlhttprequest-ssl@​1.5.3
	number-is-nan@​1.0.1
	safer-buffer@​2.1.2
	typedarray@​0.0.6
	path-parse@​1.0.6
	tty-browserify@​0.0.0
	safe-buffer@​5.1.2
	object-assign@​4.1.1
	pinkie-promise@​2.0.1
	path-is-inside@​1.0.2
	shebang-regex@​1.0.0
	to-array@​0.1.4
	os-browserify@​0.3.0
	restore-cursor@​2.0.0
	parsejson@​0.0.3
	static-extend@​0.1.2
	parseqs@​0.0.5
	strip-ansi@​4.0.0 ⏵ 3.0.1
	trim-right@​1.0.1
	p-try@​1.0.0
	parseuri@​0.0.5
	set-blocking@​2.0.0
	object-copy@​0.1.0
	setimmediate@​1.0.5
	setprototypeof@​1.1.0
	proto-list@​1.2.4
	unique-slug@​2.0.1
	strict-uri-encode@​1.1.0
	path-browserify@​0.0.0
	selenium-server@​3.14.0
See 308 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		[email protected] has a Critical CVE. CVE: GHSA-h7cp-r72f-jxh6 pbkdf2 returns predictable uninitialized/zero-filled memory for non-normalized or unimplemented algos (CRITICAL) Affected versions: >= 3.0.10 < 3.1.3 Patched version: 3.1.3 From: commercialoperator/frontend/commercialoperator/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-v62p-rq8g-8h59 pbkdf2 silently disregards Uint8Array input, returning static keys (CRITICAL) Affected versions: < 3.1.3 Patched version: 3.1.3 From: commercialoperator/frontend/commercialoperator/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-95m3-7q98-8xr5 sha.js is missing type checks leading to hash rewind and passing on crafted data (CRITICAL) Affected versions: < 2.4.12 Patched version: 2.4.12 From: commercialoperator/frontend/commercialoperator/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-qm95-pgcg-qqfq Insufficient validation when decoding a Socket.IO packet (CRITICAL) Affected versions: >= 4.0.0 < 4.0.5; >= 4.1.0 < 4.2.1; < 3.3.3; >= 3.4.0 < 3.4.2 Patched version: 3.3.3 From: commercialoperator/frontend/commercialoperator/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-cf4h-3jhx-xvhq Arbitrary Code Execution in underscore (CRITICAL) Affected versions: >= 1.3.2 < 1.12.1 Patched version: 1.12.1 From: commercialoperator/frontend/commercialoperator/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-h4j5-c7cj-74xg xmlhttprequest and xmlhttprequest-ssl vulnerable to Arbitrary Code Injection (CRITICAL) Affected versions: < 1.6.2 Patched version: 1.6.2 From: commercialoperator/frontend/commercialoperator/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-72mh-269x-7mh5 Improper Certificate Validation in xmlhttprequest-ssl (CRITICAL) Affected versions: < 1.6.1 Patched version: 1.6.1 From: commercialoperator/frontend/commercialoperator/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: commercialoperator/frontend/commercialoperator/package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report