Insecure State Generation in laravel/socialite
Priority LOW 38CWE-331Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix Fixed laravel/socialite (Packagist): 2.0.9
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | laravel/socialite (Packagist) | 1.0.0 to before 2.0.9 | 2.0.9 | Patch available | GHSA-h97c-qp24-439v |
- laravel/socialite (Packagist) Vendor— Affected 1.0.0 to before 2.0.9 Fixed in 2.0.9 Patch available GHSA-h97c-qp24-439v
Remediation
- Fix · GHSA-h97c-qp24-439v laravel/socialite (Packagist) Fixed in 2.0.9 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-h97c-qp24-439v
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences