CVE-2026-62322 python-social-auth CVE debrief

Who should care

Defenders who use the Python Social Auth library with the LINE backend should assess their exposure and verify that the OAuth state validation is properly implemented. This includes reviewing the LINE backend configuration, ensuring that the OAuth state validation is properly implemented, and monitoring for potential attacks using the LINE backend. Additionally, defenders should review the application code to ensure that the fix is properly applied and to

Why it matters

Defenders should care about this vulnerability because it allows an attacker to gain unauthorized access to a victim’s account using the LINE backend of Python Social Auth.

• An attacker can log in as the victim using the attacker-controlled LINE account.
• An attacker can link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path.

Technical summary

The LINE backend of Python Social Auth did not validate the returned OAuth state, allowing an attacker to start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. This vulnerability allows an attacker to gain unauthorized access to a victim’s account using the LINE backend of Python Social Auth. The vulnerability can be exploited by an attacker to log in as the victim using the attacker-controlled LINE account or link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path.

Defensive priority

Defenders should prioritize verifying the LINE backend configuration and ensuring that the OAuth state validation is properly implemented.

Recommended defensive actions

• Verify the LINE backend configuration and ensure that the OAuth state validation is properly implemented.
• Review the application code to ensure that the fix is properly applied.
• Monitor for potential attacks using the LINE backend.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.

Evidence notes

The evidence for this vulnerability comes from the CVE Program record and the source item provided by osv_dev. The details of the vulnerability are limited to the information provided in these sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.