Authentication bypass by nonce replay in the Laravel Socialite Facebook provider

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-73683?

CVE-2026-73683 is a vulnerability classified as Authentication Bypass by Capture-replay, affecting Socialite (affected versions: < 5.29.0). This vulnerability is rated Critical, with a CVSS score of 9.2. Current sources do not report this vulnerability as exploited.

Overview

Original source data

Laravel Socialite's Facebook provider contains an authentication bypass vulnerability that allows unauthenticated attackers to replay captured OIDC id_tokens by exploiting the missing nonce claim validation in the getUserByOIDCToken() function within FacebookProvider.php. Attackers who obtain a valid, unexpired id_token issued for the same Facebook App ID can submit the captured token to the backend userFromToken() endpoint, bypassing authentication controls because signature, aud, and iss checks pass while no session-bound nonce comparison is performed, resulting in unauthorized access to victim accounts.

Affected products and scope

  • Laravel Socialite is marked affected by default.
  • Socialite versions less than 5.29.0 under semver are affected.
  • The CNA advisory identifies commit caf714f as the patch. The related pull request was merged into the 5.x branch; the available evidence does not provide a separate branch-by-branch release statement beyond the affected boundary above.

Technical details

The flaw is in Socialite's Facebook provider, specifically getUserByOIDCToken() in FacebookProvider.php. Before the fix, the provider checked the token signature and the aud and iss claims but did not compare the token's nonce with a session or request-bound expected nonce. An attacker who obtains a valid, unexpired id_token issued for the same Facebook App ID can therefore replay it through the backend userFromToken() flow. The key precondition is possession of that valid token; the record states that no prior attacker privileges or user interaction are required, while the token-acquisition requirement makes the attack high complexity. The patch adds a nonce parameter to userFromToken(), stores the expected nonce, obtains it through getExpectedNonce(), and rejects a missing or mismatched nonce using hash_equals. How a token is captured or obtained, and how the application maps the Socialite identity to account permissions, remain deployment-dependent.

Exploitability

The vulnerability is reachable over the network through an application's backend userFromToken() processing path for Facebook OIDC. An attacker requires no prior authentication and no user interaction, but must obtain a valid, unexpired id_token for the same Facebook App ID, making token acquisition the main attack difficulty. The supplied record marks public_exploit as false; CISA enrichment returned with the record reports exploitation as none and automatable as no. Those statuses describe the available evidence and do not prove that future abuse is impossible.

Technical impact

The technical result is an authentication bypass at the application's Facebook OIDC token boundary, not a Facebook signature forgery; the token must still be valid, unexpired, and issued for the same App ID. If the application maps the token to an existing account, the attacker may receive access in that account's context. Subsequent read, write, or administrative actions depend on the permissions granted to the victim account. The record does not describe server-side code execution, cross-tenant access, or privilege expansion beyond the account reached.

Business impact

Successful exploitation can cause the application to treat an attacker as the authenticated user associated with the affected account. Depending on that account's permissions and the application's design, consequences may include access to private data, unauthorized data changes, actions performed on the user's behalf, or disruption of account functions. The risk is most significant where Facebook OIDC identity is directly linked to an internal account. Actual organizational impact depends on victim-account privileges and application behavior after Socialite returns the identity; the record does not establish a specific breach or data exposure.

Remediation

  1. Update Laravel Socialite out of the affected range below 5.29.0 to code containing the nonce fix identified by commit caf714f, and verify the resolved package version in the lockfile and deployment artifact.
  2. Ensure every Facebook OIDC flow supplies the expected nonce to the provider and rejects tokens with a missing or mismatched nonce, matching the patched behavior.
  3. If an immediate update is not possible, temporarily disable or isolate the Facebook OIDC token flow until equivalent nonce validation is enforced. This is an application-level mitigation, not a CNA-published workaround.
  4. Review all userFromToken() call sites and test the correct-nonce, incorrect-nonce, missing-expected-nonce, and missing-token-nonce cases after updating.
  5. Assess authentication events and account changes associated with Facebook OIDC during the period when an affected version was deployed. Failure to find suspicious activity does not rule out prior token replay.

Detection

  • Inventory deployed Laravel Socialite versions and package lockfiles, identifying versions less than 5.29.0.
  • Identify applications using the Facebook provider, Facebook Limited Login OIDC, getUserByOIDCToken(), or userFromToken().
  • Verify that each authentication flow creates a nonce for the authentication transaction and supplies the expected nonce to token validation.
  • Test in a controlled environment that a token with a missing nonce or a mismatched nonce is rejected, consistent with the patch behavior.
  • If application logs expose the relevant authentication data, review successful Facebook OIDC logins where nonce validation was absent or failed. This is precautionary monitoring, not a confirmed IOC; absence of such log evidence does not establish safety.
Sources (18)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.