CVE-2026-81906

Concrete CMS OAuth callback login path prior to version 9.5.3 did not check whether an account was active or email-validated before establishing a session. A deactivated or unvalidated user with an existing OAuth binding could complete authentication and receive a session that was fully...

CVE-2026-18122: Missing Authorization

Concrete CMS 9.2.0 to 9.5.2 Express REST API list endpoint exposes restricted Express entries via Missing Authorization; the Concrete CMS REST API's Express entry collection endpoint disabled the per-entry view permission check. An OAuth token with read scope for an Express entity could enumerate...

PT-2026-89996

Concrete CMS 9.2.0 to 9.5.2 Express REST API list endpoint exposes restricted Express entries via Missing Authorization; the Concrete CMS REST API's Express entry collection endpoint disabled the per-entry view permission check. An OAuth token with read scope for an Express entity could enumerate...

CVE-2026-81906: Authentication Bypass Using an Alternate Path or Channel

Concrete CMS OAuth callback login path prior to version 9.5.3 did not check whether an account was active or email-validated before establishing a session. A deactivated or unvalidated user with an existing OAuth binding could complete authentication and receive a session that was fully...

Fedora 45 : perl-Net-OAuth (2026-27bab0e213)

The remote Fedora 45 host has a package installed that is affected by a vulnerability as referenced in the FEDORA-2026-27bab0e213 advisory. Net::OAuth versions before 0.33 for Perl check HMAC-SHA1, HMAC-SHA256 and PLAINTEXT signatures with a non- constant-time comparison in verify. This update...

CVE-2026-81906

Concrete CMS prior to version 9.5.3 is affected by an OAuth callback login flaw. The vulnerable component is the OAuth callback login path , which failed to verify whether an account was active or email-validated before establishing a session. As a result, a deactivated or unvalidated user with a...

CVE-2026-81906 [UNREVIEWED] OAuth Callback Login Bypasses Deactivated-Account Checks

Concrete CMS OAuth callback login path prior to version 9.5.3 did not check whether an account was active or email-validated before establishing a session. A deactivated or unvalidated user with an existing OAuth binding could complete authentication and receive a session that was fully...

CVE-2026-81906 [UNREVIEWED] OAuth Callback Login Bypasses Deactivated-Account Checks

Concrete CMS OAuth callback login path prior to version 9.5.3 did not check whether an account was active or email-validated before establishing a session. A deactivated or unvalidated user with an existing OAuth binding could complete authentication and receive a session that was fully...

CVE-2026-81906 [UNREVIEWED] OAuth Callback Login Bypasses Deactivated-Account Checks

Concrete CMS OAuth callback login path prior to version 9.5.3 did not check whether an account was active or email-validated before establishing a session. A deactivated or unvalidated user with an existing OAuth binding could complete authentication and receive a session that was fully...

Open WebUI: Users denied by the OAuth role policy can still sign in via token exchange

Summary Open WebUI's OAuth token exchange endpoint issues a session for a provider access token without running the OAuth role management that the normal OAuth login callback runs. A user whose provider roles the login callback would refuse, or would demote, could still obtain a working session a...

GHSA-WVM9-9G5J-623F Open WebUI: Users denied by the OAuth role policy can still sign in via token exchange

Summary Open WebUI's OAuth token exchange endpoint issues a session for a provider access token without running the OAuth role management that the normal OAuth login callback runs. A user whose provider roles the login callback would refuse, or would demote, could still obtain a working session a...

Incorrect Authorization

Overview open-webui is an Open WebUI Affected versions of this package are vulnerable to Incorrect Authorization via the OAuth token exchange process. An attacker can retain unauthorized access to roles, including administrative privileges, by exchanging a valid provider access token even after t...

EUVD-2026-75170

Open WebUI: Unauthenticated requests can stall the server via uncached OIDC fetches in back-channel logout...

GHSA-WPMR-8H3Q-FWJ7 Open WebUI: Sign-in as another user via wildcard characters in the OAuth subject claim on SQLite

Summary On SQLite deployments, the lookup that maps an external identity to a local account does a substring match instead of an exact match. A subject value containing SQL wildcard characters therefore matches accounts the value was never issued for, and the sign-in binds to whichever account th...

Open WebUI: Sign-in as another user via wildcard characters in the OAuth subject claim on SQLite

Summary On SQLite deployments, the lookup that maps an external identity to a local account does a substring match instead of an exact match. A subject value containing SQL wildcard characters therefore matches accounts the value was never issued for, and the sign-in binds to whichever account th...

EUVD-2026-75176

Open WebUI: Sign-in as another user via wildcard characters in the OAuth subject claim on SQLite...

EUVD-2026-73162

n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution...

NPM: n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

NPM: n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution vulnerability discovered by ? in WordPress Npm n8n versions 2.37.7...

n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

Impact The OAuth token endpoint bound an authorization code's first access token to the consented resource, but not its refresh token. Refreshing only checked that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could refres...

GHSA-CW9W-VV67-HF73 n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

Impact The OAuth token endpoint bound an authorization code's first access token to the consented resource, but not its refresh token. Refreshing only checked that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could refres...