Insecure State Generation in laravel/socialite
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (laravel/socialite 2.0.9), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist laravel/socialite
- Affected
- >= 1.0.0, < 2.0.9
- Fixed in
- 2.0.9
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-h97c-qp24-439v lists affected ranges: Packagist laravel/socialite >=1.0.0 <2.0.9
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
laravel/socialite versions prior to 2.0.9 are found to have an insecure state generation mechanism, potentially exposing the OAuth authentication process to security risks. The issue has been addressed in version 2.0.9 by ensuring that the state is generated using a truly random approach, enhancing the security of the OAuth flow.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-h97c-qp24-439v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-h97c-qp24-439v Advisory: Insecure State Generation in laravel/socialite IDs: GHSA-h97c-qp24-439v Record: https://patchnext.com/advisories/ghsa-h97c-qp24-439v (revision 1, source checked 26 Oct 2026, 14:24 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: laravel/socialite 2.0.9. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist laravel/socialite: affected >= 1.0.0, < 2.0.9; fixed in 2.0.9 ## Suggested inspection (read-only) - Packagist laravel/socialite: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on laravel/socialite. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-h97c-qp24-439v (GitHub-reviewed advisory GHSA-h97c-qp24-439v lists affected ranges: Packagist laravel/socialite >=1.0.0 <2.0.9) Commands are suggestions: review each one before running it.
Loading voting…