94939 matches found
CVE-2026-77130
The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key...
EUVD-2026-65345
The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key...
CVE-2026-77130
The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key...
CVE-2026-77130
The TYPO3 extension SYSSY – TYPO3 Monitoring & Security Checks (syssy) fails to properly validate the expiration of a client-supplied JWT token . This allows an attacker who already holds a valid SYSSY project API key to continue authenticating with an expired token , effectively bypassing sessio...
CVE-2026-77130 Insufficient Session Expiration in extension "SYSSY - TYPO3 Monitoring & Security Checks" (syssy)
The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key...
CVE-2026-77134 Broken Access Control in extension "femanager" (femanager)
The extension fails to require the dedicated admin confirmation token when processing an admin-approval request, so a regular user confirmation hash, obtainable by any visitor through the public resend-confirmation action, is sufficient to self-approve a pending account awaiting admin approval...
CVE-2026-77134 Broken Access Control in extension "femanager" (femanager)
The extension fails to require the dedicated admin confirmation token when processing an admin-approval request, so a regular user confirmation hash, obtainable by any visitor through the public resend-confirmation action, is sufficient to self-approve a pending account awaiting admin approval...
EUVD-2026-65342
The extension fails to require the dedicated admin confirmation token when processing an admin-approval request, so a regular user confirmation hash, obtainable by any visitor through the public resend-confirmation action, is sufficient to self-approve a pending account awaiting admin approval...
CVE-2026-77134
The extension fails to require the dedicated admin confirmation token when processing an admin-approval request, so a regular user confirmation hash, obtainable by any visitor through the public resend-confirmation action, is sufficient to self-approve a pending account awaiting admin approval...
CVE-2026-77134 Broken Access Control in extension "femanager" (femanager)
The extension fails to require the dedicated admin confirmation token when processing an admin-approval request, so a regular user confirmation hash, obtainable by any visitor through the public resend-confirmation action, is sufficient to self-approve a pending account awaiting admin approval...
Insecure Default Initialization Of Resource
org.openidentityplatform.openam, openam-core is vulnerable to Insecure Default Initialization of Resource. The vulnerability is due to the default configuration setting the iPlanetDirectoryPro SSO cookie with HttpOnly=false while also using the cookie as a CSRF token in OAuth/OIDC flows, which...
CVE-2026-65633
Improper Authentication vulnerability in team-alembic AshAuthentication allows purpose-limited JWTs to be replayed as full bearer API credentials when a resource uses stateless bearer-token verification. The bearer-token authentication helper AshAuthentication.Plug.Helpers.retrievefrombearer/3...
CVE-2026-65633 Purpose-limited JWT accepted as full bearer authentication in AshAuthentication
Improper Authentication vulnerability in team-alembic AshAuthentication allows purpose-limited JWTs to be replayed as full bearer API credentials when a resource uses stateless bearer-token verification. The bearer-token authentication helper AshAuthentication.Plug.Helpers.retrievefrombearer/3...
CVE-2026-65633
AshAuthentication (team-alembic) contains an improper authentication flaw where the stateless bearer-token helper retrieve_from_bearer/3 fails to verify that a JWT's purpose claim equals user. When a resource uses the default require_token_presence_for_authentication?: false, purpose-limited toke...
EUVD-2026-65322
Improper Authentication vulnerability in team-alembic AshAuthentication allows purpose-limited JWTs to be replayed as full bearer API credentials when a resource uses stateless bearer-token verification. The bearer-token authentication helper AshAuthentication.Plug.Helpers.retrievefrombearer/3...
CVE-2026-65633 Purpose-limited JWT accepted as full bearer authentication in AshAuthentication
Improper Authentication vulnerability in team-alembic AshAuthentication allows purpose-limited JWTs to be replayed as full bearer API credentials when a resource uses stateless bearer-token verification. The bearer-token authentication helper AshAuthentication.Plug.Helpers.retrievefrombearer/3...
EEF-CVE-2026-65633 Purpose-limited JWT accepted as full bearer authentication in AshAuthentication
Summary Improper Authentication vulnerability in team-alembic AshAuthentication allows purpose-limited JWTs to be replayed as full bearer API credentials when a resource uses stateless bearer-token verification. The bearer-token authentication helper...
CVE-2026-65633 Purpose-limited JWT accepted as full bearer authentication in AshAuthentication
Improper Authentication vulnerability in team-alembic AshAuthentication allows purpose-limited JWTs to be replayed as full bearer API credentials when a resource uses stateless bearer-token verification. The bearer-token authentication helper AshAuthentication.Plug.Helpers.retrievefrombearer/3...
Authentication Bypass
Keycloak is vulnerable to an authentication bypass. The vulnerability is due to missing brute-force protection validation in the CIBA token redemption handler, which allows an attacker with valid client credentials to obtain access and refresh tokens for a user whose account was locked after the...
Authorization Bypass
Keycloak is vulnerable to Authorization Bypass. The vulnerability is due to the token exchange feature ignoring tenant restrictions, where the restriction check is bypassed and an attacker with a valid Microsoft token from a different organization can gain access to the Keycloak realm...