228092 matches found
CVE-2026-104033
A vulnerability exists in SSSD where the software fails to correctly treat an LDAP shadow expiration value of zero as an expired account. When configured to enforce account expiration via LDAP, this access control bypass allows a user with valid credentials for a deactivated account to authentica...
EUVD-2026-92890
A flaw was found in SSSD. When configured to enforce account expiration using LDAP Lightweight Directory Access Protocol shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass...
CVE-2026-104033
A flaw was found in SSSD. When configured to enforce account expiration using LDAP Lightweight Directory Access Protocol shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass...
CVE-2026-104033 Sssd: sssd: access control bypass via improper ldap shadow expiration check
A flaw was found in SSSD. When configured to enforce account expiration using LDAP Lightweight Directory Access Protocol shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass...
CVE-2026-104033 Sssd: sssd: access control bypass via improper ldap shadow expiration check
A flaw was found in SSSD. When configured to enforce account expiration using LDAP Lightweight Directory Access Protocol shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass...
CVE-2026-104033
A flaw was found in SSSD. When configured to enforce account expiration using LDAP Lightweight Directory Access Protocol shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass...
Kimai-CVE-2026-52824-POC
Kimai CVE-2026-52824 — Default APPSECRET Authentication Bypass Note: The repository URL contains an outdated CVE ID CVE-2026-49865. The correct and current CVE tracked in this repository is CVE-2026-52824 GHSA-jr9p-4h4j-6c58. Proof-of-concept exploit toolkit for the hardcoded default APPSECRET...
CVE-2026-106307: Incorrect Authorization
Incorrect authorization in Network in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to bypass system access restrictions via a crafted HTML page. Chromium security severity: Medium...
PT-2026-106312
A vulnerability has been found in PickMall Lilishop up to 4.2.4. This affects an unknown function of the file /buyer/trade/receipt of the component Buyer Invoice List. Such manipulation of the argument memberId leads to authorization bypass. It is possible to launch the attack remotely. The explo...
PT-2026-106851
Authentication bypass OAuth device authorization flow in Devolutions Server 2026.3.7.0 and earlier allows a remote attacker to take over a user's account via replay of a captured device verification link by an authenticated victim...
PT-2026-107237
Name of the Vulnerable Software and Affected Versions QnABot on AWS versions 7.0.0 through 7.4.5 Description An authorization bypass exists in the optional Amazon Q Business Lambda hook sample. This issue occurs due to a user-controlled key, which may allow an authenticated remote user to read...
The Model Plants the Trigger: Answer-Side Backdoor Attacks in Multi-Turn Large Language Models
Safety alignment in Large Language Models LLMs remains vulnerable to backdoor attacks. Existing LLM backdoors are almost all input-centric: activation depends on explicit trigger patterns in the user input, so modern guardrails are built to sanitize the input space. We challenge this assumption...
PT-2026-107037
Name of the Vulnerable Software and Affected Versions Google Chrome versions prior to 155.0.8059.39 Description Missing authorization in the Animation component allows a remote attacker to bypass the web origin policy, which is a security mechanism that restricts how a document or script loaded...
PT-2026-107110
Name of the Vulnerable Software and Affected Versions Devolutions Server versions prior to 2026.3.7.1 Description An authentication bypass exists in the Azure AD external login flow. A remote attacker can take over a user account by replaying a captured login-session token that is exposed within ...
PT-2026-106863
Confused deputy in SignIn in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker to bypass system access restrictions into a privileged page via a crafted HTML page. Chromium security severity: Medium...
PT-2026-106359
Insufficient verification of data authenticity CWE-345 in the external OIDC login callback in Cloud Foundry UAA v4.5.0 to v79.6.0 inclusive allows an authenticated UAA user to bypass the OAuth authorization-code exchange and establish an authenticated external-OIDC browser session, via submitting...
PT-2026-106959
Name of the Vulnerable Software and Affected Versions Google Chrome versions prior to 155.0.8059.39 Description A confused deputy issue in the Omnibox allows a remote attacker to bypass the web origin policy through the use of crafted network traffic. A confused deputy is a security situation whe...
CVE-2026-106205: Missing Authorization
Missing authorization in Passwords in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. Chromium security severity: Medium...
PT-2026-106873
Name of the Vulnerable Software and Affected Versions Google Chrome versions prior to 155.0.8059.39 Description Missing authorization in the FileSystem component allows a remote attacker who has compromised the renderer process to bypass the web origin policy, which is a security mechanism that...
CVE-2026-105305: Improper Authentication
A flaw was found in the OIDC implementation of Keycloak, specifically within the Device Authorization Grant flow. This component allows devices with limited input capabilities to obtain security tokens. The issue occurs because the flow fails to check the minimum authentication level required by ...