https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 12:35:25 +0000 https://db.gcve.eu/vuln/cve-2026-88952 <p><strong>Affected:</strong> team-alembic ash_authentication</p> <p>Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker to be signed in as another user by linking an OAuth2 identity to an account that is not theirs.</p> <p>AshAuthentication.Strategy.OAuth2.UserResolver.resolve/3 matches an existing account using the register action&#39;s upsert_identity keys, then gates linking the incoming provider identity to it on email_trusted?/2, which reads only the provider&#39;s email_verified boolean and never compares the provider&#39;s email value with the matched account&#39;s email. That gate assumes the account was matched by its email field, so under any other upsert_identity it is vacuous and an attacker presenting their own verified email is attached to, and issued a session for, an account matched on some other attribute. The same unguarded gate applies in OAuth2.SignInPreparation on the registration_enabled? false path, where the account is matched by the sign-in action&#39;s read filter instead. The upsert also rewrites the matched account&#39;s email to the attacker&#39;s address, so later account recovery reaches the attacker rather than the owner.</p> <p>This issue affects ash_authentication: from 4.14.0 before 4.15.0 and from 5.0.0-rc.10 before 5.0.0-rc.14.</p> <p><strong>Affected:</strong> team-alembic ash_authentication</p> <p>Improper Authentication vulnerability in team-alembic AshAuthentication allows an attacker to be signed in as another user by linking an OAuth2 identity to an account that is not theirs.</p> <p>AshAuthentication.Strategy.OAuth2.UserResolver.resolve/3 matches an existing account using the register action&#39;s upsert_identity keys, then gates linking the incoming provider identity to it on email_trusted?/2, which reads only the provider&#39;s email_verified boolean and never compares the provider&#39;s email value with the matched account&#39;s email. That gate assumes the account was matched by its email field, so under any other upsert_identity it is vacuous and an attacker presenting their own verified email is attached to, and issued a session for, an account matched on some other attribute. The same unguarded gate applies in OAuth2.SignInPreparation on the registration_enabled? false path, where the account is matched by the sign-in action&#39;s read filter instead. The upsert also rewrites the matched account&#39;s email to the attacker&#39;s address, so later account recovery reaches the attacker rather than the owner.</p> <p>This issue affects ash_authentication: from 4.14.0 before 4.15.0 and from 5.0.0-rc.10 before 5.0.0-rc.14.</p> https://db.gcve.eu/vuln/cve-2026-88952