Authentication
Authentication is the process of verifying who a user claims to be — typically through passwords, tokens, certificates, biometrics, or hardware authenticators. It is distinct from authorization, which determines what an authenticated user is allowed to do, and the two failure modes are different: a correctly authenticated user can still be a victim of broken access control, and a perfectly authorized request can still come from a forged identity.
Modern authentication relies on layered standards: OAuth 2.0 for delegated access, OpenID Connect for federated identity, SAML for enterprise SSO, JWT for stateless session tokens, and FIDO2/WebAuthn for phishing-resistant passkeys. Each of these has well-documented attack surface — OAuth redirect_uri bypasses, SAML XML signature wrapping, MFA fatigue and AiTM phishing, session fixation, and credential stuffing remain among the most common root causes in real-world breaches.
The shift toward passkeys represents the biggest practical improvement in years: public-key credentials bound to a specific origin eliminate phishing, credential stuffing, and password reuse in one stroke. But the long tail of legacy authentication — password reset flows, OAuth implementations, SAML assertion handling, and MFA bypass paths — continues to produce critical findings across bug bounty programs.
This page collects research, writeups, tools, and standards covering authentication attacks and defenses: OAuth and SAML vulnerabilities, MFA bypass techniques, passkey rollouts, session management, and the OWASP cheat sheets that codify what good authentication looks like.
From OWASP Authentication Cheat Sheet
Authentication rarely breaks at the password
Login form attacks get the attention, and the actual failures are usually elsewhere: in the flows built around authentication rather than the credential check itself. Password reset, account recovery, email change, multi-factor enrolment, session invalidation, remembered devices, social login linking — each is a path to an authenticated session, and each tends to receive far less review than the login page, while offering the same outcome.
Password reset is the most consistently productive of these. Tokens that are predictable, that do not expire, that are not invalidated on use, or that are not bound to the requesting account; host header injection that sends a valid reset link to an attacker-controlled domain; responses that differ enough to enumerate which addresses are registered. Account linking is close behind: if a social identity can be attached to an account by email address without verifying control of it, the entire authentication model collapses to whether an attacker can claim an address.
Multi-factor implementation errors follow their own patterns. The check that only applies to one of several login paths. The verification endpoint with no rate limit, making a six-digit code exhaustible. The backup-code mechanism that is weaker than the factor it backs up. And the persistent one: a session established before MFA is completed that is already sufficiently privileged.
OAuth and OIDC deserve care because they are protocols people integrate
rather than implement, and the failure modes are in the integration —
unvalidated or loosely-matched redirect_uri values leaking codes,
missing state allowing CSRF on the callback, implicit flow
leftovers, and tokens accepted without verifying issuer and audience.
Session handling closes the loop: predictable identifiers, no rotation on privilege change, tokens that survive logout or password change, and overlong-lived refresh tokens. The material below covers credential storage too, but the flows are where the findings are.
| Date Added | Link | Excerpt |
|---|---|---|
| 2026-11-19 NEW 2026 | CVE-2026-123002: How I Found a 2FA Bypass in Gitea and Wrote the Patch news | A critical vulnerability in Gitea (versions up to 28.3.0) allowed for a two-factor authentication (2FA) bypass. The issue stemmed from a lack of rate limiting on TOTP (Time-based One-Time Password) code submissions. Attackers with a stolen password could brute-force the six-digit TOTP code in approximately 11 minutes by sending around 800 requests per second. This bypass affected sign-in, password reset flows, and Basic authentication via the X-Gitea-OTP header. The author of this report identified the bug, explained the underlying mathematics, and contributed a patch to address the vulnerability. → infosecwriteups.com |
| 2026-11-19 NEW 2026 | Incus authentication bypass news | Incus versions prior to 7.6.0 are vulnerable to an authentication bypass. This vulnerability allows unauthorized access to the system. Users are strongly advised to update to Incus 7.6.0 or later to mitigate this security risk. |
| 2026-11-19 NEW 2026 | NocoDB OAuth authentication bypass news | NocoDB versions prior to 2026.10.1 have a critical vulnerability allowing authentication bypass. This means unauthorized users could gain access to the system without proper credentials. The exploit targets the OAuth authentication flow, potentially exposing sensitive data and compromising system integrity. Users are strongly advised to upgrade to version 2026.10.1 or later to patch this security flaw. |
| 2026-11-19 NEW 2026 | I Changed USER to ADMIN in a JWT. Here’s Why the API Rejected It. intermediate API Sec JWT | This article explores a common security vulnerability involving JSON Web Tokens (JWTs). The author attempted to manipulate a JWT by changing the "USER" claim to "ADMIN" to gain elevated privileges. However, the API rejected this modification. The explanation delves into why this happened, highlighting the importance of JWT validation and how APIs typically prevent such unauthorized access. The core takeaway is that simply altering a JWT claim is insufficient to bypass authentication or authorization mechanisms if the token's integrity is properly verified. |
| 2026-11-19 NEW 2026 | Tensei auth bypass via hard-coded JWT secret intermediate JWT Secrets | Writeup of CVE-2026-129552 in Tensei, detailing an authentication bypass vulnerability in @tensei/auth. When JWT_SECRET is unset, the application reverts to a hard-coded signing key, 'auth-secret-key'. This allows unauthenticated attackers to forge JWTs with any user ID, including administrators, by leveraging the populateContextFromToken function. |
| 2026-11-19 NEW 2026 | CAST Imaging hardcoded Keycloak auth token news Secrets | Library of code snippets and techniques for identifying hardcoded credentials. This summary focuses on GHSA-3rm5-vmc4-7vm6, a vulnerability in CAST Imaging v3.6.2 where a hardcoded Keycloak authentication token within the "KeyCloakController" class allows unauthenticated access to user enumeration and API token hash retrieval via the "/api/auth/keycloak/users" endpoint. Attackers with source code or configuration access can exploit this token for reconnaissance. |
| 2026-11-19 NEW 2026 | Authentication vs Authorization: The Difference, and How to Actually Secure an API beginner API Sec AuthZ | Authentication verifies *who* a user is, confirming their identity, while authorization determines *what* that verified user is allowed to do. Confusing these two fundamental security concepts is a primary reason for API breaches. Secure API design requires distinct, robust implementation of both authentication and authorization mechanisms to prevent unauthorized access and actions. |
| 2026-11-19 NEW 2026 | Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 news 10 min read RCE | Vulnerabilities CVE-2026-123633 and CVE-2026-123007 are critical unauthenticated remote code execution flaws discovered independently by Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint in NGINX software, impacting its HTTP/2 handling. Exploitation allows attackers to gain control of NGINX servers, potentially leading to data theft or service disruption, even when backend applications are secure. These memory-safety issues, a use-after-free and an invalid memory copy, have existed for years and are exploitable with HTTP/2 enabled. → wiz.io |
| 2026-11-18 NEW 2026 | Exploiting Replay Protected Monotonic Counters to Brute-Force Windows Hello PINs advanced 2 min read | Writeup on exploiting Replay Protected Monotonic Counters (RPMCs) to brute-force Windows Hello PINs. The analysis details implementation flaws in Winbond SPI flash and AMD's NV controller, including HMAC key leakage via voltage glitching and incorrect RPMC increment verification. These vulnerabilities enable rollback of the fTPM's non-volatile state, allowing a 4-digit PIN to be recovered in 40 hours, and also impact BitLocker's TPM+PIN pre-boot protection. → arxiv.org |
| 2026-11-18 NEW 2026 | Stop Reading JWT Claims Everywhere in Your Angular Application beginner JWT | In "Stop Reading JWT Claims Everywhere in Your Angular Application," Dipak Ahirav addresses a common inefficiency in Angular development. The article highlights the practice of repeatedly parsing JSON Web Tokens (JWTs) across various components and services. Ahirav proposes a more optimized approach, suggesting that JWT claims should be read and processed once, with the relevant data then being stored and accessed from a central location. This aims to improve performance and maintainability within Angular applications by avoiding redundant decoding operations. |
| 2026-11-18 NEW 2026 | CIRCUTOR PowerStudio: JWT alg=none identity forgery advanced JWT | This research details a critical vulnerability in CIRCUTOR PowerStudio, allowing for JWT alg=none identity forgery. This flaw enables attackers to perform a 0-day RCE chain, posing a significant risk to enterprise, ICS/SCADA, ERP, and NMS products. The research provides full root-cause analyses and reproducible Proofs of Concept for this severe security exploit. |
| 2026-11-18 NEW 2026 | Why Your Logout Button Doesn’t Log Out a JWT beginner JWT | A JWT (JSON Web Token) represents a promise that remains valid until its expiration date, irrespective of any action taken by the user. Consequently, a logout button in an application typically cannot invalidate an already issued JWT. This is because the server hosting the JWT has no inherent mechanism to know if the user has requested to log out. To effectively manage JWTs, strategies like token blacklisting or implementing short-lived tokens with refresh tokens are necessary. |
| 2026-11-18 NEW 2026 | CVE-2026-120387: PowerStudio SCADA JWT signature validation bypass news JWT | Writeup detailing CVE-2026-120387, an authentication bypass vulnerability in CIRCUTOR PowerStudio SCADA WAVE. This flaw allows unauthenticated remote attackers to impersonate users by submitting an unsigned JSON Web Token (JWT) with the algorithm set to "none." The application's JWT validation component fails to verify the cryptographic signature, granting unauthorized access to protected functionality and user privileges. |
| 2026-11-18 NEW 2026 | Farmasimplex shared OAuth credentials news Secrets | Farmasimplex, a healthcare software solution, inadvertently exposed OAuth credentials. These credentials, used for third-party application authentication, were discoverable within the CeliachiaRL integration component distributed with the software. This vulnerability could have allowed unauthorized access to user data and functionalities connected through OAuth. The issue has since been addressed. |
| 2026-11-18 NEW 2026 | N-able N-central predictable credential news Secrets | N-able N-central versions prior to 2026.4.1 HF3 are vulnerable to a predictable credential flaw. This vulnerability allows attackers to potentially gain unauthorized access by exploiting the predictable nature of credentials. Users are strongly advised to update their N-able N-central installations to the patched version to mitigate this security risk. |
| 2026-11-18 NEW 2026 | A token can be valid and still not be meant for your API intermediate API Sec JWT | A valid token doesn't automatically mean it's intended for your API. Even if a JSON Web Token (JWT) is correctly signed and has an expiration date, it might not be issued for your specific service. This is a crucial security consideration, especially when working with OAuth2 and frameworks like Spring Boot. Developers should verify that the token's issuer and audience claims align with their API's expectations to prevent potential vulnerabilities. |
| 2026-11-18 NEW 2026 | P2 Broken Access Control Allowing Unauthorized Account Email Modification and Account Takeover news AuthZ Bug Bounty | A P2 High severity vulnerability of Broken Access Control was discovered, allowing unauthorized users to modify account emails. This vulnerability leads to Account Takeover. The Bugcrowd VRT classifies this under Broken Access Control. |
| 2026-11-18 NEW 2026 | How Trusting a Request Header Turned a Password Reset Into Account Takeover intermediate AuthZ Bug Bounty | This article details a web security vulnerability where trusting a request header led to account takeover during a password reset process. The bug is described as a distinct type, differing from common vulnerabilities like IDOR and race conditions. The core issue stemmed from improper validation of a specific request header, which attackers could manipulate to hijack password reset flows and gain unauthorized access to user accounts. |
| 2026-11-18 NEW 2026 | How a Login Link Could Switch kChat to an Attacker’s Server intermediate Bug Bounty Mobile | Researchers discovered a high-severity Android vulnerability in kChat related to deep link validation. The flaw allowed an attacker to craft a malicious login link. When a user clicked this link, it could trick kChat into sending push tokens to an attacker-controlled server. This disclosure of push tokens could then enable the attacker to intercept or potentially send messages on behalf of the user, compromising communication security. |
| 2026-11-18 NEW 2026 | Login CSRF via a replayable OAuth code (static state, no PKCE) intermediate 4 min read Bug Bounty CSRF | Writeup detailing login CSRF via a replayable OAuth code where a static `state` parameter, lack of PKCE, and absence of session binding allowed an authorization code minted in one browser to log a different browser into the attacker's account. The vulnerability arises from the absence of these three key invariants, enabling session confusion and allowing attackers to trick victims into performing actions within an attacker-controlled account. Remediation involves implementing per-request `state`, enforcing PKCE, and binding code consumption to the initiating browser. |
| 2026-11-18 NEW 2026 | OAuth-based CSRF: exploiting a flawed state parameter intermediate 5 min read CSRF | Writeup on OAuth-based CSRF exploiting a flawed state parameter. This analysis details how a mature product's "Connect with Facebook" flow was vulnerable to account takeover due to an improperly implemented `state` parameter. The `state` was found to be static and predictable, failing its role as a CSRF defense. The writeup explains the attack vector, highlighting how an attacker could hijack a victim's account by crafting a link that, when processed by the victim's browser, erroneously linked the attacker's Facebook identity to the victim's account. It also outlines best practices for correct OAuth `state` parameter implementation, including generating cryptographically random values, binding them to the session, and performing constant-time validation. |
| 2026-11-18 NEW 2026 | NamelessMC: OAuth callback state not validated, login CSRF news 3 min read CSRF | Advisory regarding NamelessMC's OAuth login callback handling, detailing a login CSRF and session swapping vulnerability. The application fails to validate the `state` parameter server-side, allowing an attacker to craft a callback URL. If a victim initiates an OAuth login flow and then navigates to this attacker-controlled URL, their session can be authenticated as the attacker's linked NamelessMC account, leading to unintended authentication and potential account contamination. |
| 2026-11-18 NEW 2026 | Prime CMS auth bypass via createUser GraphQL mutation intermediate 2 min read GraphQL | Writeup of CVE-2026-129941 in Prime CMS, detailing an authentication bypass via the `createUser` GraphQL mutation. Unauthenticated attackers can exploit a commented-out authentication guard and hard-coded admin roles to gain full administrative control. The vulnerability, classified under CWE-306, is network-reachable, unauthenticated, and requires no user interaction, posing a critical technical impact. |
| 2026-11-17 NEW 2026 | Cyrus SASL SRP authentication bypass intermediate | Writeup of GHSA-h9fw-9v74-m2cr, detailing an authentication bypass in Cyrus SASL's SRP server mechanism. Versions up to 2.1.28 are affected due to `srp_server_mech_step2` failing to reject client public values `A` that are multiples of `N`. This allows unauthenticated network clients to authenticate as any user by sending `A` equal to `N`, forcing a zero shared secret and obtaining session keys. |
| 2026-11-17 NEW 2026 | 5 JWT Authentication Bugs I Keep Seeing in Django REST Framework Projects intermediate JWT Python | This article details five common JWT authentication bugs found in Django REST Framework projects. Drawing from extensive debugging experience, the author provides practical, actionable fixes for each issue. The focus is on simplifying secure authentication within DRF, addressing recurring vulnerabilities that can arise despite the apparent simplicity of JWT. |
| 2026-11-17 NEW 2026 | AdminNeo authentication bypass in ClickHouse driver intermediate | AdminNeo versions prior to 5.9.1 have an authentication bypass vulnerability. This flaw allows unauthorized access to ClickHouse driver functionalities without proper credentials. |
| 2026-11-17 NEW 2026 | I Steal Your Login With One Query Parameter: My OAuth Account-Takeover Playbook advanced Bug Bounty | This content details a method for account takeover using the "Sign in with Google" feature. The author outlines a playbook for exploiting vulnerabilities within the OAuth authentication flow. The technique involves manipulating a single query parameter to gain unauthorized access to user accounts on various applications. The primary focus is on demonstrating a specific attack vector that compromises the security of integrations relying on Google's sign-in functionality. → thexssrat.medium.com |
| 2026-11-17 NEW 2026 | How an Unhandled Unicode Normalization Mismatch Led to a $5,000 Account Takeover intermediate Bug Bounty | An unhandled Unicode normalization mismatch allowed for account takeovers, leading to a $5,000 bounty. This vulnerability arose from inconsistencies in how an application's authentication layer and its database handled character encoding. Attackers could exploit this by submitting specially crafted input that appeared identical but was interpreted differently by each system, ultimately enabling unauthorized access to user accounts. The issue highlights the critical importance of consistent character encoding handling in web applications to prevent security breaches. |
| 2026-11-17 NEW 2026 | SourceHut disabled registration bypass via login CSRF token (CVE-2026-121728) news 3 min read CSRF | Writeup detailing CVE-2026-121728, a bypass of SourceHut's disabled registration via a login CSRF token. The vulnerability stems from a logic bug introduced during a frontend to GraphQL backend refactor, where the registration form handler failed to check if registration was closed on the successful path. Attackers could exploit this by submitting a POST request to `/register/step2` using a CSRF token obtained from the `/login` endpoint, thereby creating an account even when registration was officially disabled. Affected versions span from 0.56.11 through 0.88.9. |
| 2026-11-17 NEW 2026 | Keystatic login CSRF intermediate CSRF | Writeup of GHSA-fv6w-2c5w-h387, detailing a login cross-site request forgery vulnerability in Keystatic through 0.6.9. This flaw, specifically in the githubOauthCallback handler, allows unauthenticated remote attackers to impersonate victims by omitting state validation in the OAuth callback. Attackers can trick victims into visiting a malicious callback URL, resulting in unintended actions committed under the attacker's GitHub identity. |
| 2026-11-16 NEW 2026 | DefaultLdapRealm authentication caching bypass intermediate | Library advisory GHSA-3j37-vw7v-fxxw detailing a DefaultLdapRealm authentication caching bypass in Apache Shiro. When authentication caching is enabled, successful logins allow subsequent authentication with any password by skipping the LDAP bind and utilizing the default AllowAllCredentialsMatcher. This vulnerability affects Shiro versions through 3.0.0, and can be mitigated by upgrading to 3.0.1+, disabling caching, or configuring a valid credentials matcher. |
| 2026-11-16 NEW 2026 | CVE-2026-62374: SD-JWT JS verification bypass news 2 min read JWT | Writeup detailing CVE-2026-62374, a verification bypass in OpenWallet Foundation's SD-JWT JS library. Versions 0.19.0 and earlier of `@sd-jwt/core` and `@sd-jwt/decode` fail to enforce RFC 9901 §7.1, allowing silent claim-set reduction attacks. This occurs due to permissive UTF-8 decoding and a lack of mandatory reference checks for disclosures, enabling attackers to strip claims while maintaining cryptographic signature validity. Remediation involves updating to `@sd-jwt/core` version 0.20.0 and implementing fail-closed schema validation. |
| 2026-11-16 NEW 2026 | SilentAir Hijacks Asian Telecom Networks to Intercept SMS 2FA Codes and Spy on Taiwanese Users news 5 min read Mobile | Library for detecting SilentAir, a spying group that has hijacked Asian telecom networks by exploiting SS7 and Diameter protocols to intercept SMS 2FA codes and spy on users, primarily in Taiwan. The group used hacked equipment to send UpdateLocation messages, diverting calls and texts, and also deployed silent SMS campaigns for reconnaissance. The techniques involved attacks on the IPX network, and potential links to the Liminal Panda group using tools like SCTPE/SIGweaver and the GTPDoor backdoor were noted. → thehackernews.com |
| 2026-11-16 NEW 2026 | IBM ContextForge MCP Gateway auth bypass intermediate AI | IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11 contain a vulnerability that could allow an unauthenticated attacker to bypass security restrictions. This bypass enables the attacker to access sensitive information within the system. The vulnerability is present in the authentication mechanism of the MCP Gateway. |
| 2026-11-16 NEW 2026 | [CVE-2026–126187] — Unauthenticated RCE in React Server Components’ Flight Protocol news RCE | A critical vulnerability, CVE-2026–126187, has been identified in React Server Components' Flight protocol. This flaw allows for unauthenticated Remote Code Execution (RCE). The Flight protocol is the communication mechanism used by RSC. This vulnerability poses a significant security risk, enabling attackers to execute arbitrary code on a server without prior authentication. |
| 2026-11-16 NEW 2026 | Authlib accepts OpenSSH keys/certs as HMAC secrets intermediate JWT Python | Library update addressing CVE-2024-37568, where Authlib incorrectly accepted OpenSSH keys and certificates as HMAC secrets for algorithms like HS256. This allowed attackers to forge tokens by using a known public key. The vulnerability impacted `authlib.jose` if algorithms weren't explicitly restricted. Patched in version 1.9.5, the fix prevents OctKey from loading OpenSSH public keys or certificates. Workarounds include algorithm restriction or using typed keys. |
| 2026-11-16 NEW 2026 | GraphQL Core Schema: critical account takeover news 2 min read AuthZ GraphQL | Library module SA-CONTRIB-2026-316 (CVE-2026-126725) for Drupal's GraphQL Core Schema allows account takeover by enabling the "User Login" schema extension. This critical vulnerability permits any authenticated user to change another account's password if the extension is enabled. Affected versions are prior to 1.0.29, with an upgrade to 1.0.29 being the recommended fix, or disabling the "User Login" extension as a mitigation. |
| 2026-11-15 NEW 2026 | Vvveb 1.0.9.0 authentication bypass in generateCookie() news | Vvveb versions prior to 1.0.9.0 are vulnerable to an authentication bypass. This vulnerability exists within the `generateCookie()` function. Attackers can exploit this flaw to gain unauthorized access to the system by bypassing authentication mechanisms. Updating to Vvveb version 1.0.9.0 or later is recommended to patch this security issue. |
| 2026-11-15 NEW 2026 | CAP JWT claims validation bypass using non-canonical claim names news 2 min read JWT | Library for validating JWT claims, specifically addressing CVE-2026-19194. This vulnerability in HashiCorp's cap JWT validation library before version 0.14.0 allows for a bypass of claims validation by using non-canonical claim names. Attackers controlling JWT contents could exploit this inconsistency to bypass issuer or subject expectations, with the security impact depending on the consuming application's usage of returned claims. The fix is available in cap 0.14.0. → ibm.com |
| 2026-11-15 NEW 2026 | JWT Pitfalls: What Goes Wrong and How to Avoid It beginner JWT | This content outlines common mistakes related to JSON Web Tokens (JWTs) that compromise security, as warned by JWT specifications and OWASP. It details eight specific pitfalls and explains how each weakens defenses. Crucially, it provides essential checks that JWT verifiers must implement to prevent these vulnerabilities. The focus is on understanding and mitigating security risks associated with JWT implementation. |
| 2026-11-15 NEW 2026 | Fast Logins You Can Still Revoke: Sessions, JWTs, and Refresh Tokens Explained beginner | This content explains a two-step login process designed for speed, minimizing database queries during each request. It details how sessions, JSON Web Tokens (JWTs), and refresh tokens work together to achieve this. The system allows for revoking user access across all devices, enhancing security by enabling immediate logouts. |
| 2026-11-15 NEW 2026 | OpenBao authentication bypass news Secrets | An authentication bypass vulnerability exists in OpenBao versions prior to 2.6.5 and 2.7.2. This flaw allows unauthorized access to the system without proper authentication. Users are advised to upgrade to patched versions to mitigate this security risk. |
| 2026-11-15 NEW 2026 | XWEB EVO hardcoded backdoor password news Secrets | Advisory for XWEB EVO before 5.6.2 detailing a hardcoded backdoor password, xwebevonewgeneration, enabling unauthenticated remote administrative access. This vulnerability, identified as CVE-2026-124004, allows attackers to acquire a full administrator session with a single request. The product line reached end of service in March 2026. |
| 2026-11-15 NEW 2026 | NocoDB authentication bypass in oauth-token.service news API Sec | NocoDB versions prior to 2026.08.1 are vulnerable to an authentication bypass flaw in the oauth-token.service. This vulnerability allows unauthorized access to NocoDB instances. Users are strongly advised to update to a patched version to mitigate this security risk. |
| 2026-11-15 NEW 2026 | Exploiting All 10 OWASP API Security Risks in vAPI (+ Bonus Arena Challenges) intermediate API Sec AuthZ Bug Bounty | This content details a comprehensive walkthrough of exploiting all ten OWASP API Security Risks within vAPI, including bonus arena challenges. The process covers identifying and exploiting vulnerabilities such as Broken Object Level Authorization and Broken Authentication. The focus is on a practical, step-by-step approach to understanding and mitigating these critical API security flaws. |
| 2026-11-15 NEW 2026 | How a Cache Keys Mismatch Led to a Web Cache Deception Account Takeover intermediate Bug Bounty | A web cache deception vulnerability, stemming from a mismatch in cache keys, allowed for account takeovers. This issue arises when a caching layer, like a CDN, processes requests differently than the origin server. Attackers can exploit this by crafting specific requests that cause sensitive user data, such as session cookies, to be cached and served to other users. The vulnerability allows attackers to effectively hijack other users' accounts by tricking the cache into returning their session information. |
| 2026-11-15 NEW 2026 | Pre-Auth Account Takeover via Broken Password Reset in a Legacy Mobile API intermediate Bug Bounty Mobile | An attacker could take over user accounts without authentication on a legacy mobile API due to a flaw in the password reset mechanism. This vulnerability allowed unauthorized access by exploiting the insecure reset process before a user logged in. |
| 2026-11-15 NEW 2026 | SUSE-SU-2026:5064-1: PyJWT HMAC forgery and JWKS key-substitution fixes news 4 min read JWT Python | Update for python-PyJWT addressing eight vulnerabilities, including CVE-2026-101917 and CVE-2026-102267. This fixes issues related to JWKS endpoint amplification, unauthenticated request exceptions, forwarded credential disclosure, HMAC token forgery, raw-token revocation checks, CPU consumption, and sender-constrained token misuse. |
| 2026-11-15 NEW 2026 | graphql-orm-router: HTTP SSE/multipart subscriptions bypass WebSocket gateway auth controls intermediate 4 min read API Sec AuthZ GraphQL | Library for enforcing HTTP subscription authorization in GraphQL applications. This library addresses a medium severity vulnerability (RTR-2) where Server-Sent Events (SSE) and multipart subscriptions bypass WebSocket gateway authentication. Specifically, these HTTP subscription methods failed to enforce mandatory bearer tokens, token expiry, or attempt limits, allowing anonymous or expired access. The vulnerability stems from the router’s mishandling of HTTP subscription requests, bypassing the intended authorization checks that apply to WebSocket connections. A suggested fix involves rejecting subscriptions off the trusted internal path or enforcing principal and expiry for HTTP streams. |
| 2026-11-14 NEW 2026 | A Valid Signature Isn’t Enough: Attributing and Validating Leaked JWTs intermediate 10 min read JWT | Library for detecting and validating leaked JSON Web Tokens (JWTs). It details manual steps using `curl`, `jq`, `openssl`, and Python to decode JWTs, check claims, retrieve public keys via OIDC discovery, and rebuild PEM files for signature verification. The library scales this process to analyze millions of leaked tokens, attributing them to specific services and identifying those still valid, covering JWTs from 14 services. → blog.gitguardian.com |
Frequently Asked Questions
- What is the difference between authentication and authorization?
- Authentication (authn) verifies who a user is — typically through passwords, tokens, certificates, or biometrics. Authorization (authz) determines what an authenticated user is allowed to do. The two are often conflated but rely on different mechanisms and fail in different ways. A correctly authenticated user can still be a victim of broken authorization, and vice versa.
- What are the most common authentication vulnerabilities?
- Common authentication flaws include credential stuffing, weak password policies, missing or bypassable multi-factor authentication, predictable session tokens, password reset poisoning, OAuth redirect_uri manipulation, SAML signature wrapping, and JWT algorithm confusion. Many real-world breaches start with authentication weaknesses rather than novel exploitation.
- Are passkeys actually more secure than passwords?
- Yes — passkeys use public-key cryptography bound to a specific origin, which eliminates phishing, credential stuffing, and password reuse attacks. The private key never leaves the user's device. Passkeys are based on the WebAuthn and FIDO2 standards and are now supported by major browsers, operating systems, and identity providers.
Weekly AppSec Digest
Get new resources delivered every Monday.