ETK-2026-1266Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.description
social-auth-core versions affected by this issue can incorrectly associate HubSpot, Monzo, or WLCG sign-ins with another local account. An attacker using an affected enabled backend may be authenticated as the account associated with an earlier login when the application has stored the shared malformed identifier. This requires the affected provider backend to be enabled and a prior association to exist.
mitigation
Upgrade social-auth-core to 6.1.1 or later. Review and remove or repair affected provider associations that use the malformed shared identifier, and investigate accounts authenticated through these backends.
fixed in 6.1.1
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-10 07:42Zghsa: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/ETK-2026-1266
{ "etk_id": "ETK-2026-1266", "cve_id": null, "display_id": "ETK-2026-1266", "ghsa_id": "GHSA-m4mf-rqrp-5pq8", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "Cross-account authentication in social-auth-core OAuth backends", "summary": "social-auth-core versions affected by this issue can incorrectly associate HubSpot, Monzo, or WLCG sign-ins with another local account. An attacker using an affected enabled backend may be authenticated as the account associated with an earlier login when the application has stored the shared malformed identifier. This requires the affected provider backend to be enabled and a prior association to exist.", "mitigation": "Upgrade social-auth-core to 6.1.1 or later. Review and remove or repair affected provider associations that use the malformed shared identifier, and investigate accounts authenticated through these backends.", "vendor": "pip", "product": "pip:social-auth-core", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 4.5.4, <= 6.1.0" ], "ecosystem": "pip", "fixed_versions": [ "6.1.1" ], "package_name": "social-auth-core", "purl": "pkg:pypi/social-auth-core" } ], "cwes": [ 287 ], "cvss_score": 7, "cvss_src": "ethiack_provisional", "cvss_vector": null, "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 13.52975095, "t0_at": null, "signals": { "trigger_signal": { "at": "2026-10-10T07:42:49+00:00", "days": -10.881013278935185, "is_lower_bound": true, "measured_at": "2026-10-21T04:51:28.571997+00:00", "url": "https://github.com/python-social-auth/social-core/security/advisories/GHSA-m4mf-rqrp-5pq8" } } }
published 2026-10-11 22:10Z
last change 2026-10-21 04:45Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.