# sessions

A session is a persistent interaction between a subscriber and an endpoint that begins with authentication and ends with termination, using a session secret presented by subscriber software.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## phpAfterShell Explained: How Hackers Could Turn a PHP Session Flaw Into Code Execution

DevFeed: [phpAfterShell Explained: How Hackers Could Turn a PHP Session Flaw Into Code Execution](<https://devfeed.tech/articles/phpaftershell-explained-how-hackers-could-turn-a-php-session-flaw-into-code-execution-144345.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/11/phpaftershell-explained-how-hackers.html>)

Author: The Hacker News

Published: 2026-11-19T16:59:56Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [PHP](<https://devfeed.tech/topics/php.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [execution](<https://devfeed.tech/topics/execution.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>)

Tags: [application-security](<https://devfeed.tech/tags/application-security.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve-2026-126714](<https://devfeed.tech/tags/cve-2026-126714.md>), [php](<https://devfeed.tech/tags/php.md>), [phpaftershell](<https://devfeed.tech/tags/phpaftershell.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [session](<https://devfeed.tech/tags/session.md>), [software-security](<https://devfeed.tech/tags/software-security.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

phpAfterShell (CVE-2026-126714) affects PHP's default file-based session handler. If a session write is interrupted at the right point, remnants of old data can be read as attacker-chosen serialized records; a later session_start() can create the object. Code execution additionally requires a suitable gadget chain or another vulnerability, and session values may also be corrupted. The tested upload-progress route writes to the session before app code runs; login requirements depend on how the app exposes session handling. PHP's fixed releases clear the session file before writing and stop if clearing fails. Update to the fixed release, rebuild and redeploy containers, and verify the PHP version serving requests. Disabling session.upload_progress.enabled is only a temporary mitigation: other attacker-controlled session data paths may remain, and the setting is on by default in older releases but off in the listed fixed releases. Non-file stores are outside this defect, though their interrupted-update behavior needs separate checking. The excerpt reports no known attacks and says the researchers' separate code-execution bug details are withheld.

### Source excerpt

phpAfterShell Explained: How Hackers Could Turn a PHP Session Flaw Into Code Execution PHP's default file-based session storage can be made to return objects an attacker chose, by cutting off a session write at the right moment. When combined with a second weakness, such as a suitable g ... Read more Published Date: Nov 19, 2026 (4 hours, 28 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-126714 CVE-2026-118383

## CVE-2026-73969 - AnsibleForms: Authentication bypass via hard-coded default JWT signing secret

DevFeed: [CVE-2026-73969 - AnsibleForms: Authentication bypass via hard-coded default JWT signing secret](<https://devfeed.tech/articles/cve-2026-73969-ansibleforms-authentication-bypass-via-hard-coded-default-jwt-signing-secret-141189.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-73969>)

Author: CVEFEED.io; github.com

Published: 2026-11-18T20:14:51Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [hardcoded credentials](<https://devfeed.tech/topics/hardcoded-credentials.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [ansibleforms](<https://devfeed.tech/tags/ansibleforms.md>), [ansibleguy76](<https://devfeed.tech/tags/ansibleguy76.md>), [api](<https://devfeed.tech/tags/api.md>), [api-access](<https://devfeed.tech/tags/api-access.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-73969](<https://devfeed.tech/tags/cve-2026-73969.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [full](<https://devfeed.tech/tags/full.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [secret](<https://devfeed.tech/tags/secret.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-service](<https://devfeed.tech/tags/self-service.md>), [signing](<https://devfeed.tech/tags/signing.md>), [token](<https://devfeed.tech/tags/token.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Before version 6.2.1, AnsibleForms could accept forged administrator JWTs when ACCESS_TOKEN_SECRET was unset: a public fallback signing secret let unauthenticated attackers create tokens with privileged claims, which the application trusted for authorization without reloading the user from the database. This enabled authentication bypass and privileged API access. The issue is fixed in version 6.2.1.

### Source excerpt

CVE ID :CVE-2026-73969 Published : Nov. 18, 2026, 8:14 p.m. | 39 minutes ago Description :AnsibleForms is a self-hosted web application that turns automation into self-service forms. Prior to 6.2.1, AnsibleForms uses a public hard-coded fallback JWT signing secret from server/config/auth.config.js when ACCESS_TOKEN_SECRET is unset. An unauthenticated attacker can sign a self-contained token with privileged claims because server/src/auth/auth_jwt.js verifies the signature without reloading the user from the database, and server/src/lib/middleware.js trusts the token's roles and options for authorization. A forged token can therefore be accepted as an administrator session, resulting in authentication bypass and full privileged API access. This issue is fixed in version 6.2.1. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-21601 - Atlassian Jira Service Management Data Center Broken Authentication and Session Management Vulnerability

DevFeed: [CVE-2026-21601 - Atlassian Jira Service Management Data Center Broken Authentication and Session Management Vulnerability](<https://devfeed.tech/articles/cve-2026-21601-atlassian-jira-service-management-data-center-broken-authentication-and-session-management-vulnerability-138219.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-21601>)

Author: cvefeed.io

Published: 2026-11-17T18:17:57Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [sessions](<https://devfeed.tech/topics/sessions.md>), [jira](<https://devfeed.tech/topics/jira.md>), [atlassian](<https://devfeed.tech/topics/atlassian.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actions](<https://devfeed.tech/tags/actions.md>), [atlassian](<https://devfeed.tech/tags/atlassian.md>), [atlassian-jira](<https://devfeed.tech/tags/atlassian-jira.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bug-bounty](<https://devfeed.tech/tags/bug-bounty.md>), [bug-bounty-program](<https://devfeed.tech/tags/bug-bounty-program.md>), [confluence](<https://devfeed.tech/tags/confluence.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-21601](<https://devfeed.tech/tags/cve-2026-21601.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-score](<https://devfeed.tech/tags/cvss-score.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [download](<https://devfeed.tech/tags/download.md>), [jira](<https://devfeed.tech/tags/jira.md>), [management](<https://devfeed.tech/tags/management.md>), [service](<https://devfeed.tech/tags/service.md>), [session](<https://devfeed.tech/tags/session.md>), [session-management](<https://devfeed.tech/tags/session-management.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

CVE-2026-21601 is a high-severity (CVSS 8.7) broken authentication and session management vulnerability in Jira Service Management Data Center, introduced in versions 10.0.0 and 11.0.0. It could let an unauthenticated attacker perform actions as another user. Atlassian recommends upgrading to the latest version; supported fixed-version options listed are 10.3.27 or later for the 10.3 line and 11.3.13 or later for the 11.3 line. The excerpt does not identify exact affected versions.

### Source excerpt

CVE ID :CVE-2026-21601 Published : Nov. 17, 2026, 6:17 p.m. | 32 minutes ago Description :This High severity BASM (Broken Authentication & Session Management) vulnerability was introduced in versions 10.0.0 and 11.0.0 of Jira Service Management Data Center. This BASM (Broken Authentication & Session Management) vulnerability, with a CVSS Score of 8.7, allows an unauthenticated attacker to perform actions as another user. Atlassian recommends that Jira Service Management Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 * Jira Service Management Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://confluence.atlassian.com/servicemanagement/jira-service-management-release-notes-780083086.html). You can download the latest version of Jira Service Management Data Center from the download center (https://www.atlassian.com/software/jira/service-management/download-archives). This vulnerability was discovered by Nagli and reported via our Bug Bounty program Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-130070 - Ghost (muneeb141) Authentication Bypass via bypass\_otp in convert\_to\_real\_user

DevFeed: [CVE-2026-130070 - Ghost (muneeb141) Authentication Bypass via bypass\_otp in convert\_to\_real\_user](<https://devfeed.tech/articles/cve-2026-130070-ghost-muneeb141-authentication-bypass-via-bypass-otp-in-convert-to-real-user-136273.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-130070>)

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-16T22:18:22Z

Content type: article

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [branch](<https://devfeed.tech/tags/branch.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [call](<https://devfeed.tech/tags/call.md>), [client](<https://devfeed.tech/tags/client.md>), [commit](<https://devfeed.tech/tags/commit.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-130070](<https://devfeed.tech/tags/cve-2026-130070.md>), [email](<https://devfeed.tech/tags/email.md>), [existing](<https://devfeed.tech/tags/existing.md>), [ghost](<https://devfeed.tech/tags/ghost.md>), [muneeb141](<https://devfeed.tech/tags/muneeb141.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-tokens](<https://devfeed.tech/tags/oauth-tokens.md>), [otp](<https://devfeed.tech/tags/otp.md>), [parameter](<https://devfeed.tech/tags/parameter.md>)

### AI overview

The excerpt reports a critical authentication bypass in Ghost (muneeb141), affecting the main branch from commit c731cdf through 672dfec. The whitelisted convert_to_real_user method accepts a client-supplied bypass_otp=1, allowing an unauthenticated attacker to skip OTP verification. The described path uses the guest-accessible create_ghost_session endpoint to obtain a ghost session, then calls convert_to_real_user with an arbitrary real_email to receive OAuth tokens for an existing account. The excerpt rates the vulnerability 9.3 but provides no exact affected versions or mitigation details.

### Source excerpt

CVE ID :CVE-2026-130070 Published : Nov. 16, 2026, 10:18 p.m. | 36 minutes ago Description :Ghost by muneeb141 on the main branch from commit c731cdf through commit 672dfec contains an authentication bypass vulnerability in the whitelisted ghost.api.ghost.convert_to_real_user method that allows unauthenticated attackers to skip OTP verification by setting the client-supplied bypass_otp parameter. Attackers can obtain a ghost session from the guest-accessible create_ghost_session endpoint, then call convert_to_real_user with an arbitrary real_email and bypass_otp=1 to receive OAuth tokens for existing accounts and take them over. Severity: 9.3 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## SCKit Worm Installs Rogue ScreenConnect Clients and Session Cookie Relays Across Hundreds of Endpoints

DevFeed: [SCKit Worm Installs Rogue ScreenConnect Clients and Session Cookie Relays Across Hundreds of Endpoints](<https://devfeed.tech/articles/sckit-worm-installs-rogue-screenconnect-clients-and-session-cookie-relays-across-hundreds-of-endpoints-130068.md>)

Original publisher: [Read original article](<https://www.huntress.com/blog/sckit-worm-rogue-screenconnect>)

Author: Ben Nahorney; Susannah Matt

Published: 2026-11-12T02:00:00Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>), [Huntress Blog](<https://devfeed.tech/sources/huntress-blog.md>)

Topics: [Endpoint Security & XDR](<https://devfeed.tech/topics/endpoint-security-xdr.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2026](<https://devfeed.tech/tags/2026.md>), [clients](<https://devfeed.tech/tags/clients.md>), [contributions](<https://devfeed.tech/tags/contributions.md>), [cookie](<https://devfeed.tech/tags/cookie.md>), [cve](<https://devfeed.tech/tags/cve.md>), [deal](<https://devfeed.tech/tags/deal.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [martin](<https://devfeed.tech/tags/martin.md>), [max](<https://devfeed.tech/tags/max.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [rogers](<https://devfeed.tech/tags/rogers.md>), [rogue](<https://devfeed.tech/tags/rogue.md>), [sckit](<https://devfeed.tech/tags/sckit.md>), [screenconnect](<https://devfeed.tech/tags/screenconnect.md>), [thanks](<https://devfeed.tech/tags/thanks.md>), [this](<https://devfeed.tech/tags/this.md>), [update](<https://devfeed.tech/tags/update.md>), [worm](<https://devfeed.tech/tags/worm.md>), [writeup](<https://devfeed.tech/tags/writeup.md>)

### AI overview

Huntress attributes the November 11, 2026 ScreenConnect incident to a flaw in RMM+ versions 1.0.31 and 1.0.32: when no access key was configured, the extension accepted a blank key and bypassed ScreenConnect accounts, roles, and MFA. Commands pushed rogue ScreenConnect clients and SCKit to at least 288 hosts across 48 Huntress customer organizations. SCKit installs persistence and is designed to relay stolen technician session cookies through ScreenConnect to spread to other reachable endpoints, but investigators had not observed that lateral spread succeed. ConnectWise disabled RMM+ and several related extensions in hosted environments and urged on-premises partners to do likewise. Defenders should review Run Command and Toolbox history, check for rogue clients and RelayTrap persistence, isolate suspected hosts, avoid connecting through ScreenConnect, and investigate from out-of-band tools. From a clean device, revoke exposed sessions and rotate credentials; keep hosts isolated until persistence is removed and reinfection checks are complete.

### Source excerpt

SCKit Worm Installs Rogue ScreenConnect Clients and Session Cookie Relays Across Hundreds of Endpoints Acknowledgments: Special thanks to Sharon Martin, Ben Bernstein, Andrew Brandt, Jamie Levy, Max Rogers, Lindsey Welch, and Aaron Deal for their contributions to this investigation and writeup.Update: ... Read more Published Date: Nov 12, 2026 (9 hours, 24 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-84869 CVE-2021-40444

## CVE-2026-89324 - Basel Post Types \<= 1.18 - Unauthenticated Authentication Bypass via Forged Opauth Callback Signature with Hardcoded Fallback Salt

DevFeed: [CVE-2026-89324 - Basel Post Types \<= 1.18 - Unauthenticated Authentication Bypass via Forged Opauth Callback Signature with Hardcoded Fallback Salt](<https://devfeed.tech/articles/cve-2026-89324-basel-post-types-1-18-unauthenticated-authentication-bypass-via-forged-opauth-callback-signature-with-hardcoded-fallback-salt-127477.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-89324>)

Author: CVEFEED.io; wordfence.com

Published: 2026-11-10T22:21:14Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [MFA](<https://devfeed.tech/topics/mfa.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [app](<https://devfeed.tech/tags/app.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [callback](<https://devfeed.tech/tags/callback.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [compute](<https://devfeed.tech/tags/compute.md>), [config](<https://devfeed.tech/tags/config.md>), [cookie](<https://devfeed.tech/tags/cookie.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-89324](<https://devfeed.tech/tags/cve-2026-89324.md>), [email](<https://devfeed.tech/tags/email.md>), [error](<https://devfeed.tech/tags/error.md>), [fallback](<https://devfeed.tech/tags/fallback.md>), [post-types](<https://devfeed.tech/tags/post-types.md>), [salt](<https://devfeed.tech/tags/salt.md>)

### AI overview

Basel Post Types versions through 1.18 have a critical authentication bypass caused by a malformed `defined()` check in `BASEL_Auth::get_config()`. The check fails and leaves the plugin using a publicly visible hardcoded fallback salt, allowing an attacker to forge an Opauth callback signature offline. Through the unauthenticated callback handler, a forged request tied to a target account's email can grant a session as that user, including an administrator, without password, MFA, or ownership checks. Exploitation requires active WooCommerce and at least one configured Basel social-login provider (Facebook, Google, or VKontakte) with valid app credentials.

### Source excerpt

CVE ID :CVE-2026-89324 Published : Nov. 10, 2026, 10:21 p.m. | 10 minutes ago Description :The Basel Post Types plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.18. The vulnerability exists because a missing-quotes coding error in the defined() call for SECURE_AUTH_SALT inside BASEL_Auth::get_config() causes PHP to evaluate the constant's value rather than its name, making the check always fail and permanently falling back to the static hardcoded salt 2NlBUibcszrVtNmDnxqDbwCOpLWq91eatIz6O1O that is publicly visible in the theme source code; because this salt is static and known, an attacker can compute a valid Opauth signature entirely offline and submit a forged ?opauth callback to the unauthenticated init hook endpoint processed by register_or_login. This makes it possible for unauthenticated attackers to authenticate as any existing WordPress user, including administrators, by forging a callback tied to a known target account email address -- bypassing all password verification, multi-factor authentication, and ownership checks, and receiving a fully authenticated session cookie via wc_set_customer_auth_cookie(). Exploitation requires WooCommerce to be active and at least one Basel social-login provider (Facebook, Google, or VKontakte) to be configured with a valid app_id and app_secret in the theme settings. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## How to add authentication to a Rust axum app with WorkOS AuthKit

DevFeed: [How to add authentication to a Rust axum app with WorkOS AuthKit](<https://devfeed.tech/articles/how-to-add-authentication-to-a-rust-axum-app-with-workos-authkit-123473.md>)

Original publisher: [Read original article](<https://workos.com/blog/rust-axum-authentication-authkit>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Rust](<https://devfeed.tech/topics/rust.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [client library](<https://devfeed.tech/topics/client-library.md>)

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [request](<https://devfeed.tech/tags/request.md>), [rust](<https://devfeed.tech/tags/rust.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [service](<https://devfeed.tech/tags/service.md>), [webhook](<https://devfeed.tech/tags/webhook.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

The WorkOS Rust SDK lets an axum service authenticate with AuthKit using sealed session cookies and locally verified access tokens. The source outlines the flow: build and share a client, create a PKCE authorization URL while storing the verifier and state in a short-lived sealed cookie, exchange the callback code, then authenticate the session on each request. Cookie passwords must be 64-character hex strings; the Rust cookie format is not compatible with other WorkOS SDKs. Local verification fetches and caches signing keys, but cannot detect session revocation until the access token expires, so the source recommends webhook handling and rechecks before destructive operations when revocation matters. For webhooks, verify the signature against the timestamp and exact raw body before parsing; deliveries may repeat or arrive out of order, so record processed event IDs and return 200 promptly. SDK retries cover 429s, 5xxs and retryable transport errors, but unsafe HTTP methods retry only when given an idempotency key--and only if the endpoint deduplicates it.

### Source excerpt

Use the WorkOS Rust SDK to sign users in with AuthKit, verify their session on every request, and check webhook signatures in an axum service.

## SSO is broken? The answer is already in your session log

DevFeed: [SSO is broken? The answer is already in your session log](<https://devfeed.tech/articles/sso-is-broken-the-answer-is-already-in-your-session-log-124330.md>)

Original publisher: [Read original article](<https://workos.com/blog/sso-broken-session-log>)

Author: WorkOS

Published: 2026-11-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [log management](<https://devfeed.tech/topics/log-management.md>)

Tags: [configuration](<https://devfeed.tech/tags/configuration.md>), [customer](<https://devfeed.tech/tags/customer.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [events](<https://devfeed.tech/tags/events.md>), [failed](<https://devfeed.tech/tags/failed.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [it](<https://devfeed.tech/tags/it.md>), [sso](<https://devfeed.tech/tags/sso.md>), [status](<https://devfeed.tech/tags/status.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS session logs can pinpoint where an SSO failure occurs and who can fix it. In the dashboard, filter a connection's Sessions tab by email, status, origin or time, then inspect the IdP request, response and any error. Success shifts investigation to app handling or authorization; failed sessions may point to the IdP or to your attribute mapping. Required attributes that are missing can fail sign-in, while unmapped optional attributes return null and may leave a successful session with empty fields. Origin helps distinguish app-started, IdP-started and Admin Portal test flows; OIDC is SP-initiated only. For patterns, use SSO events with connection IDs and error details: stream them to Datadog or count failures by connection through the cursor-paginated Events API. When the IdP is responsible, share the session ID, timestamp, status and response with its administrator.

### Source excerpt

Every WorkOS SSO attempt records its status, origin and the IdP's response. Read it in five minutes and know whether the fix is yours or the customer's.

## CVE-2026-85295 - Chartbrew: Full account takeover via JWTs accepted under default CB\_SECRET

DevFeed: [CVE-2026-85295 - Chartbrew: Full account takeover via JWTs accepted under default CB\_SECRET](<https://devfeed.tech/articles/cve-2026-85295-chartbrew-full-account-takeover-via-jwts-accepted-under-default-cb-secret-121677.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-85295>)

Author: CVEFEED.io; github.com

Published: 2026-11-06T21:17:10Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [chartbrew](<https://devfeed.tech/tags/chartbrew.md>), [charts](<https://devfeed.tech/tags/charts.md>), [compose](<https://devfeed.tech/tags/compose.md>), [container](<https://devfeed.tech/tags/container.md>), [create](<https://devfeed.tech/tags/create.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-85295](<https://devfeed.tech/tags/cve-2026-85295.md>), [depomo](<https://devfeed.tech/tags/depomo.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-compose](<https://devfeed.tech/tags/docker-compose.md>), [fallback](<https://devfeed.tech/tags/fallback.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [id](<https://devfeed.tech/tags/id.md>), [issue](<https://devfeed.tech/tags/issue.md>), [secret](<https://devfeed.tech/tags/secret.md>)

### AI overview

Before Chartbrew 5.2.3, four authentication helpers accepted session JWTs signed with CB_SECRET, enabling an attacker who knows a weak, known, or default secret to forge an HS256 token and impersonate a chosen user across the API and socket layer, bypassing that user's password and two-factor authentication. The description identifies stock source and repository Docker Compose deployments as affected; a bare container with CB_SECRET undefined is not affected through this fallback path. The issue is fixed in version 5.2.3.

### Source excerpt

CVE ID :CVE-2026-85295 Published : Nov. 6, 2026, 9:17 p.m. | 53 minutes ago Description :Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, four authentication helpers accepted session tokens signed with CB_SECRET, including known, weak, or shipped-default values. The vulnerable surface is session JWT fallback in server/modules/verifyToken.js, verifyUser.js, getUserFromToken.js, and socketManager.js across the API and socket layer. A stock source or repository Docker Compose deployment retains a known, weak, or default CB_SECRET and an attacker submits a forged HS256 token decoding to a target user id. Knowing the symmetric secret lets the attacker create a token that the legacy verification fallback accepts as the target user without that user's password or two-factor authentication. The condition includes stock source and repository Docker Compose installs and any otherwise known or weak CB_SECRET; a bare container where CB_SECRET is undefined is not affected by this fallback path. A forged session impersonates the chosen user across the entire API and socket layer and exercises that user's Chartbrew privileges. This issue is fixed in version 5.2.3. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Researchers Bypass ChatGPT Lockdown Mode to Exfiltrate Chats Without User Interaction

DevFeed: [Researchers Bypass ChatGPT Lockdown Mode to Exfiltrate Chats Without User Interaction](<https://devfeed.tech/articles/researchers-bypass-chatgpt-lockdown-mode-to-exfiltrate-chats-without-user-interaction-119622.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/11/researchers-bypass-chatgpt-lockdown.html>)

Author: The Hacker News

Published: 2026-11-05T16:42:32Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [ChatGPT](<https://devfeed.tech/topics/chatgpt.md>), [Hacking](<https://devfeed.tech/topics/hacking.md>), [spoofing](<https://devfeed.tech/topics/spoofing.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [a-patched-chatgpt-html-preview-flaw-let-crafted-content-bypass-lockdown-mode-restrictions](<https://devfeed.tech/tags/a-patched-chatgpt-html-preview-flaw-let-crafted-content-bypass-lockdown-mode-restrictions.md>), [account](<https://devfeed.tech/tags/account.md>), [act](<https://devfeed.tech/tags/act.md>), [actions](<https://devfeed.tech/tags/actions.md>), [actor](<https://devfeed.tech/tags/actor.md>), [aes](<https://devfeed.tech/tags/aes.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [details](<https://devfeed.tech/tags/details.md>), [enabling-chat-data-exfiltration](<https://devfeed.tech/tags/enabling-chat-data-exfiltration.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [introduced](<https://devfeed.tech/tags/introduced.md>), [more](<https://devfeed.tech/tags/more.md>), [openai](<https://devfeed.tech/tags/openai.md>), [openai-chatgpt](<https://devfeed.tech/tags/openai-chatgpt.md>), [patched](<https://devfeed.tech/tags/patched.md>), [this](<https://devfeed.tech/tags/this.md>), [user](<https://devfeed.tech/tags/user.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

A flaw in ChatGPT's HTML preview handling let popup content escape the sandbox and bypass Lockdown Mode, creating a route for silent chat data exfiltration, phishing, or malware delivery. Check Point said nested sandboxed frames allowed a popup to use an unmodified window-opening function; content opened that way no longer faced the same restrictions. An attacker could introduce crafted content through a prompt, malicious GPT, or shared chat. The report says the issue was not limited to the Electron desktop app and that OpenAI patched it on September 18, 2026. The finding illustrates that Lockdown Mode's protections could be undermined by weaknesses in surrounding application features.

### Source excerpt

Researchers Bypass ChatGPT Lockdown Mode to Exfiltrate Chats Without User Interaction Cybersecurity researchers have disclosed details of a now-patched vulnerability that could be exploited to bypass Lockdown Mode protections in OpenAI ChatGPT. Lockdown Mode was introduced by the artif ... Read more Published Date: Nov 05, 2026 (6 hours, 8 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2025-51591

## CVE-2026-54375 - VitaFit Android \< 2.8.1.0 Long-Lived Session Token Exposure

DevFeed: [CVE-2026-54375 - VitaFit Android \< 2.8.1.0 Long-Lived Session Token Exposure](<https://devfeed.tech/articles/cve-2026-54375-vitafit-android-2-8-1-0-long-lived-session-token-exposure-117785.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-54375>)

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-04T21:54:23Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [android](<https://devfeed.tech/tags/android.md>), [application](<https://devfeed.tech/tags/application.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [backups](<https://devfeed.tech/tags/backups.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-54375](<https://devfeed.tech/tags/cve-2026-54375.md>), [management](<https://devfeed.tech/tags/management.md>), [session-management](<https://devfeed.tech/tags/session-management.md>), [token](<https://devfeed.tech/tags/token.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

VitaFit Android (com.vt.vitafit) versions before 2.8.1.0 are described as storing unencrypted m_session_id tokens in application backups; the tokens remain valid for ten years. An attacker who extracts or intercepts one can read or modify the victim's account, or delete its authentication record and block the owner's login. The excerpt lists no affected product records and provides no remediation details.

### Source excerpt

CVE ID :CVE-2026-54375 Published : Nov. 4, 2026, 9:54 p.m. | 28 minutes ago Description :VitaFit Android application (com.vt.vitafit) before 2.8.1.0 contains an insecure session management vulnerability that allows attackers to extract or intercept unencrypted m_session_id tokens stored in application backups, which remain valid for ten years. Attackers can use a stolen session token to read and modify the victim's account or delete the account's authentication record, preventing the legitimate owner from logging in again. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Vercel rolls out new protection against stolen session cookie attacks

DevFeed: [Vercel rolls out new protection against stolen session cookie attacks](<https://devfeed.tech/articles/vercel-rolls-out-new-protection-against-stolen-session-cookie-attacks-117805.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/vercel-rolls-out-new-protection-against-stolen-session-cookie-attacks/>)

Author: Bill Toulas

Published: 2026-11-04T21:31:18Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [malware protection](<https://devfeed.tech/topics/malware-protection.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [breach](<https://devfeed.tech/tags/breach.md>), [browser](<https://devfeed.tech/tags/browser.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [cookie](<https://devfeed.tech/tags/cookie.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [defense](<https://devfeed.tech/tags/defense.md>), [device](<https://devfeed.tech/tags/device.md>), [device-bound-session-credentials](<https://devfeed.tech/tags/device-bound-session-credentials.md>), [info-stealer](<https://devfeed.tech/tags/info-stealer.md>), [information-stealer](<https://devfeed.tech/tags/information-stealer.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [key](<https://devfeed.tech/tags/key.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [platform](<https://devfeed.tech/tags/platform.md>), [protection](<https://devfeed.tech/tags/protection.md>), [security](<https://devfeed.tech/tags/security.md>), [security-feature](<https://devfeed.tech/tags/security-feature.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Vercel is gradually enabling Device Bound Session Credentials (DBSC) for logins to vercel.com. DBSC binds a session cookie to a private key stored in the device's TPM, so a stolen cookie cannot be reused on another device; the key cannot be retrieved, according to Vercel's CTO. It complements Chrome's App-Bound Encryption, which makes cookie extraction harder. DBSC currently works in Chrome on macOS and Windows, and Vercel says the gradual rollout allows it to address OAuth-app edge cases. Vercel is also rolling out DPoP for its CLI. Separately, Security Review is in public beta for Pro and Enterprise teams: when enabled, Vercel Agent scans pushes to connected GitHub repositories for issues such as missing authorization checks and exposed secrets, and may validate and commit fixes if permissions allow. Scans are free until November 10, 2026; agent-generated fixes are billed separately.

### Source excerpt

Vercel is gradually rolling out Device Bound Session Credentials (DBSC) on its platform as a key defense against information stealer malware. [...]

## CVE-2026-120538 - Easy Digital Downloads \<= 3.7.2 - Unauthenticated Authentication Bypass to Administrator Account Takeover via Guest Checkout Email Binding at PayPal Capture

DevFeed: [CVE-2026-120538 - Easy Digital Downloads \<= 3.7.2 - Unauthenticated Authentication Bypass to Administrator Account Takeover via Guest Checkout Email Binding at PayPal Capture](<https://devfeed.tech/articles/cve-2026-120538-easy-digital-downloads-3-7-2-unauthenticated-authentication-bypass-to-administrator-account-takeover-via-guest-checkout-email-binding-at-paypal-capture-113137.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-120538>)

Author: CVEFEED.io; wordfence.com

Published: 2026-11-03T05:18:32Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-120538](<https://devfeed.tech/tags/cve-2026-120538.md>), [digital](<https://devfeed.tech/tags/digital.md>), [downloads](<https://devfeed.tech/tags/downloads.md>), [easy](<https://devfeed.tech/tags/easy.md>), [email](<https://devfeed.tech/tags/email.md>), [paypal](<https://devfeed.tech/tags/paypal.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [wordpress](<https://devfeed.tech/tags/wordpress.md>)

### AI overview

Easy Digital Downloads for WordPress versions through 3.7.2 are reported vulnerable to unauthenticated account takeover. In guest checkout, the plugin binds an order to an existing WordPress user solely by matching the submitted email, then PayPal capture can authenticate that user when the order's user ID matches. An attacker who uses an administrator's email and completes the PayPal purchase flow may receive an administrator session; the excerpt says the same login sink is reachable through standard PayPal checkout and the REST UnbrandedCard and Fastlane flows. The described administrator condition is that the account has no existing EDD customer record.

### Source excerpt

CVE ID :CVE-2026-120538 Published : Nov. 3, 2026, 5:18 a.m. | 30 minutes ago Description :The Easy Digital Downloads plugin for WordPress is vulnerable to authentication bypass leading to administrator account takeover in all versions up to, and including, 3.7.2. During a PayPal guest checkout, the email address entered in the guest-checkout field is trusted as proof of identity: edd_get_purchase_form_user() binds the new guest order to an existing WordPress user purely on an email-address match, rewriting the order's user_id to that user's ID. The PayPal capture sink PurchaseUser::maybe_log_in_after_capture() then looked the user up by the order email (get_user_by( 'email', $order->email )) and, when $order->user_id equalled that user's ID (which the email-binding step guarantees), issued an authenticated session with wp_set_auth_cookie(). An unauthenticated attacker who starts a guest checkout using an administrator's email address (where that administrator has no existing EDD customer record) and completes the PayPal purchase flow therefore receives an authenticated session as that administrator -- a full account takeover. The same sink is reachable through the standard PayPal checkout and the REST UnbrandedCard and Fastlane flows. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Using Claude on Amazon Bedrock with Claude Code and Cowork

DevFeed: [Using Claude on Amazon Bedrock with Claude Code and Cowork](<https://devfeed.tech/articles/using-claude-on-amazon-bedrock-with-claude-code-and-cowork-119458.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/10/31/using-claude-on-amazon-bedrock-with-claude-code-and-cowork/>)

Author: Ritesh Patel

Published: 2026-10-31T23:00:00Z

Content type: tutorial

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-marketplace](<https://devfeed.tech/tags/aws-marketplace.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-sdk](<https://devfeed.tech/tags/aws-sdk.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [browser](<https://devfeed.tech/tags/browser.md>), [budget](<https://devfeed.tech/tags/budget.md>), [cache](<https://devfeed.tech/tags/cache.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-cowork](<https://devfeed.tech/tags/claude-cowork.md>), [iam](<https://devfeed.tech/tags/iam.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Claude Code and Cowork can send model requests to Amazon Bedrock and bill them through AWS, but they use different setup and identity flows. Claude Code uses the AWS credential chain: enable Bedrock access, grant inference permissions, choose a region, and pin model IDs before rollout. Managed settings can restrict startup model checks with an allowlist on v2.1.287 or later; an allowlist alone does not enforce that restriction. Cowork is configured in Claude Desktop and deployed through MDM, with IAM Identity Center sign-in and a permission set; AWS setup runs once per organization. Cowork's in-app sign-in and named profiles provide per-user CloudTrail identity, while a shared bearer token does not. The excerpt also notes limits: Claude Code lacks WebSearch and /logout on Bedrock, uses the Invoke API rather than Converse, and gateways must preserve the eventstream response type.

### Source excerpt

Set up Claude Code and Claude Cowork on Amazon Bedrock with AWS sign-in, pinned model IDs, a managed model allowlist and the IAM policy that each one needs.

## CVE-2026-119096 - Uncanny Toolkit for LearnDash \<= 3.8.2 - Unauthenticated Authentication Bypass via 'email' Parameter

DevFeed: [CVE-2026-119096 - Uncanny Toolkit for LearnDash \<= 3.8.2 - Unauthenticated Authentication Bypass via 'email' Parameter](<https://devfeed.tech/articles/cve-2026-119096-uncanny-toolkit-for-learndash-3-8-2-unauthenticated-authentication-bypass-via-email-parameter-109662.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-119096>)

Author: CVEFEED.io; wordfence.com

Published: 2026-10-31T08:16:49Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [cve-2026-119096](<https://devfeed.tech/tags/cve-2026-119096.md>), [email](<https://devfeed.tech/tags/email.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [uncanny-toolkit-for-learndash](<https://devfeed.tech/tags/uncanny-toolkit-for-learndash.md>), [uncannyowl](<https://devfeed.tech/tags/uncannyowl.md>), [wordpress](<https://devfeed.tech/tags/wordpress.md>)

### AI overview

Uncanny Toolkit for LearnDash versions up to and including 3.8.2 has an authentication bypass in `uo_login_action()` caused by inconsistent handling of the `email` parameter. The plugin checks account status using the raw value, but WordPress `wp_signon()` sanitizes it and can still resolve the real account, allowing the check to be skipped. An unauthenticated attacker who already has a target's credentials can use this to access unverified or administrator-suspended accounts and obtain a `wordpress_logged_in` session. The required nonce is available through the unauthenticated `ult-refresh-nonce` endpoint. The supplied description rates the vulnerability 9.8, Critical.

### Source excerpt

CVE ID :CVE-2026-119096 Published : Oct. 31, 2026, 8:16 a.m. | 21 minutes ago Description :The Uncanny Toolkit for LearnDash plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 3.8.2 via the `email` parameter of the `uo_login_action()` function. This is due to a parser-differential flaw in which the plugin's account-verification gate resolves the submitted `email` value using the raw, unsanitized string passed to `get_user_by()`, while the subsequent `wp_signon()` call relies on WordPress core's internal `sanitize_user()` to strip appended junk characters -- causing the gate lookup to fail and be skipped entirely while the real account is still resolved and authenticated. This makes it possible for unauthenticated attackers to log in to unverified or administrator-suspended accounts whose credentials they already possess, obtaining a valid `wordpress_logged_in` session cookie and defeating the plugin's account-approval and account-suspension controls. The nonce required to reach the handler is freely obtainable in the same request from the unauthenticated `ult-refresh-nonce` endpoint, making exploitation trivial for any attacker with network access to the site and knowledge of a target account's credentials. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-103898 - Wp Social Login and Register Social Counter \<= 3.2.2 - Unauthenticated Authentication Bypass via Insufficient Email Verification in Social Login Callback

DevFeed: [CVE-2026-103898 - Wp Social Login and Register Social Counter \<= 3.2.2 - Unauthenticated Authentication Bypass via Insufficient Email Verification in Social Login Callback](<https://devfeed.tech/articles/cve-2026-103898-wp-social-login-and-register-social-counter-3-2-2-unauthenticated-authentication-bypass-via-insufficient-email-verification-in-social-login-callback-109655.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-103898>)

Author: CVEFEED.io; wordfence.com

Published: 2026-10-31T08:16:47Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [adapters](<https://devfeed.tech/tags/adapters.md>), [admin](<https://devfeed.tech/tags/admin.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [boolean](<https://devfeed.tech/tags/boolean.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [callback](<https://devfeed.tech/tags/callback.md>), [control](<https://devfeed.tech/tags/control.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-103898](<https://devfeed.tech/tags/cve-2026-103898.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [email](<https://devfeed.tech/tags/email.md>), [email-verification](<https://devfeed.tech/tags/email-verification.md>), [login](<https://devfeed.tech/tags/login.md>), [social](<https://devfeed.tech/tags/social.md>), [verification](<https://devfeed.tech/tags/verification.md>), [wp-social-login-and-register-social-counter](<https://devfeed.tech/tags/wp-social-login-and-register-social-counter.md>), [wpmet](<https://devfeed.tech/tags/wpmet.md>)

### AI overview

Wp Social Login and Register Social Counter versions through 3.2.2 have an authentication bypass in the social login REST callback. It finds an existing WordPress account using only the OAuth-returned email and sets an authentication cookie without checking a password. The excerpt says the email verification guard is ineffective with the bundled Hybridauth Facebook and Twitter adapters because they put the raw email string in `emailVerified`, rather than a boolean verified flag. An attacker controlling a Facebook or Twitter OAuth account that returns the registered email of an existing user may obtain a session as that user, including an Administrator. The site must have the relevant provider login configured; the excerpt says no local credentials, nonce, or prior access are required.

### Source excerpt

CVE ID :CVE-2026-103898 Published : Oct. 31, 2026, 8:16 a.m. | 21 minutes ago Description :The Wp Social Login and Register Social Counter plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 3.2.2. This is due to the social login REST callback registered at `/wp-json/wslu-social-login/type/{provider}/` with `permission_callback => __return_true` locating an existing WordPress account solely by the email string returned from the OAuth provider and calling `wp_set_auth_cookie()` without a password check, while the only verification guard -- `!empty($getProfile->emailVerified)` in `inc/admin-create-user.php` -- is a no-op for the bundled Hybridauth Facebook and Twitter adapters, both of which assign the raw email string rather than a boolean verified flag to `emailVerified`. This makes it possible for unauthenticated attackers to obtain a fully authenticated session as any existing WordPress user, including Administrators, whose registered email address can be presented through a configured Facebook or Twitter login on the target site. Exploitation requires only that the attacker control an OAuth account whose provider-returned email matches the target account's registered WordPress email address; no local credentials, nonce, or prior foothold is needed. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Delete Expired Sessions in Laravel With a Scheduled Command

DevFeed: [Delete Expired Sessions in Laravel With a Scheduled Command](<https://devfeed.tech/articles/delete-expired-sessions-in-laravel-with-a-scheduled-command-109813.md>)

Original publisher: [Read original article](<https://laravel-news.com/laravel-delete-expired-sessions>)

Author: Paul Redmond

Published: 2026-10-29T23:07:33Z

Content type: tutorial

Language: en

Sources: [Laravel](<https://devfeed.tech/sources/laravel.md>)

Topics: [Laravel](<https://devfeed.tech/topics/laravel.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [cleanup](<https://devfeed.tech/tags/cleanup.md>), [command](<https://devfeed.tech/tags/command.md>), [database](<https://devfeed.tech/tags/database.md>), [delete](<https://devfeed.tech/tags/delete.md>), [file](<https://devfeed.tech/tags/file.md>), [laravel](<https://devfeed.tech/tags/laravel.md>), [laravel-tutorials](<https://devfeed.tech/tags/laravel-tutorials.md>), [lottery](<https://devfeed.tech/tags/lottery.md>), [scheduled](<https://devfeed.tech/tags/scheduled.md>), [sessions](<https://devfeed.tech/tags/sessions.md>)

### AI overview

For Laravel 13.39 or later, apps using the `database` or `file` session driver can schedule `session:garbage-collect` to remove expired sessions, then set the session lottery to `[0, 100]` so web requests no longer run cleanup. The command uses the default driver and `session.lifetime`, reports success but not the deletion count, and does nothing for cache-based drivers. `redis`, `memcached`, `dynamodb`, `apc`, and `cookie` drivers expire sessions without cleanup. For database sessions on multiple servers, use `onOneServer()` with a shared cache lock; file sessions require running cleanup on each server unless their directory is shared. On Laravel 13.38 and earlier, schedule a closure calling the handler's `gc()` method, converting lifetime minutes to seconds; named closures are required for `onOneServer()`. The article says hourly cleanup suits the default 120-minute lifetime.

### Source excerpt

Schedule session:garbage-collect to delete expired Laravel database and file sessions, and turn off the session lottery that runs cleanup in web requests. The post Delete Expired Sessions in Laravel With a Scheduled Command appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

## CVE-2026-45049 - OpenAM Session Hijacking via CDSSO

DevFeed: [CVE-2026-45049 - OpenAM Session Hijacking via CDSSO](<https://devfeed.tech/articles/cve-2026-45049-openam-session-hijacking-via-cdsso-106980.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-45049>)

Author: CVEFEED.io; github.com

Published: 2026-10-29T22:17:02Z

Content type: article

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-45049](<https://devfeed.tech/tags/cve-2026-45049.md>), [hijacking](<https://devfeed.tech/tags/hijacking.md>), [openam](<https://devfeed.tech/tags/openam.md>), [openidentityplatform](<https://devfeed.tech/tags/openidentityplatform.md>)

### AI overview

Before OpenAM 16.1.1, the CDSSO servlet can POST a logged-in user's raw session token to an attacker-controlled URL. An attacker who lures an authenticated user to a crafted URL may capture the credential and hijack the session. Exploitation requires CDSSO to be enabled and the specified non-default configuration not to be present. The issue is fixed in OpenAM 16.1.1.

### Source excerpt

CVE ID :CVE-2026-45049 Published : Oct. 29, 2026, 10:17 p.m. | 1 hour, 5 minutes ago Description :Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, the `Cross-Domain Single Sign-On` (`CDSSO`) servlet allows a logged-in user's raw OpenAM session token to be POSTed to an attacker-controlled URL. An attacker who induces an authenticated victim to visit a crafted URL can receive the session credential and potentially hijack the session. Deployments must have `CDSSO` enabled, as is common in multi-domain deployments, and exploitation is additionally gated on a non-default configuration being absent. This issue is fixed in version 16.1.1. Severity: 8.3 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Session length vs. access token duration vs. inactivity timeout

DevFeed: [Session length vs. access token duration vs. inactivity timeout](<https://devfeed.tech/articles/session-length-vs-access-token-duration-vs-inactivity-timeout-107078.md>)

Original publisher: [Read original article](<https://workos.com/blog/session-length-access-token-duration-inactivity-timeout>)

Author: WorkOS

Published: 2026-10-29T15:42:18Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [sessions](<https://devfeed.tech/topics/sessions.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [backend](<https://devfeed.tech/tags/backend.md>), [background](<https://devfeed.tech/tags/background.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [cache](<https://devfeed.tech/tags/cache.md>), [client](<https://devfeed.tech/tags/client.md>), [clock](<https://devfeed.tech/tags/clock.md>), [clocks](<https://devfeed.tech/tags/clocks.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [database](<https://devfeed.tech/tags/database.md>), [docs](<https://devfeed.tech/tags/docs.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [timeout](<https://devfeed.tech/tags/timeout.md>), [token](<https://devfeed.tech/tags/token.md>), [vs](<https://devfeed.tech/tags/vs.md>)

### AI overview

AuthKit's three session settings run separate clocks. Maximum session length is a hard limit from sign-in; inactivity timeout ends a session when no token refresh occurs; access token duration controls how long each JWT remains valid and should not cause a visible sign-out. Shorter token lifetimes make role or permission changes and session revocation take effect sooner, but increase refresh traffic and possible refresh races. Inactivity measures refreshes rather than human activity, so background refreshes can keep a session alive; a true idle-person timeout needs an app-side activity signal. The Dashboard requires inactivity timeout to exceed token duration, with both below maximum session length. Already-issued tokens remain valid until expiry after revocation, which stops further refreshes. Settings apply per application, while clocks run per session.

### Source excerpt

Maximum session length, access token duration, and inactivity timeout each run a different clock in AuthKit. What each one controls, and how to choose it.

## CVE-2026-109516 - Bot for Telegram on WooCommerce \<= 1.3.0 - Unauthenticated Authentication Bypass to Account Takeover via Fake Telegram Webhook + Brute-Forced Login Token

DevFeed: [CVE-2026-109516 - Bot for Telegram on WooCommerce \<= 1.3.0 - Unauthenticated Authentication Bypass to Account Takeover via Fake Telegram Webhook + Brute-Forced Login Token](<https://devfeed.tech/articles/cve-2026-109516-bot-for-telegram-on-woocommerce-1-3-0-unauthenticated-authentication-bypass-to-account-takeover-via-fake-telegram-webhook-brute-forced-login-token-105761.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-109516>)

Author: CVEFEED.io

Published: 2026-10-29T03:39:13Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [bot](<https://devfeed.tech/tags/bot.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-109516](<https://devfeed.tech/tags/cve-2026-109516.md>), [fake](<https://devfeed.tech/tags/fake.md>), [header](<https://devfeed.tech/tags/header.md>), [http](<https://devfeed.tech/tags/http.md>), [login](<https://devfeed.tech/tags/login.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [rest](<https://devfeed.tech/tags/rest.md>), [server](<https://devfeed.tech/tags/server.md>), [telegram](<https://devfeed.tech/tags/telegram.md>), [token](<https://devfeed.tech/tags/token.md>), [webhook](<https://devfeed.tech/tags/webhook.md>), [woocommerce](<https://devfeed.tech/tags/woocommerce.md>)

### AI overview

Bot for Telegram on WooCommerce versions up to and including 1.3.0 reportedly allows unauthenticated account takeover. Its REST webhook accepts forged updates without Telegram signature verification and resolves an attacker-supplied chat ID as a WordPress username. The plugin then creates a login token from the request's User-Agent and time; the description says these inputs are attacker-controlled or can be bounded using the response Date header. An unauthenticated, nonce-less order endpoint redeems the token and sets an authentication cookie, potentially granting access to any account, including an administrator, if the attacker knows its username. The supplied text rates the issue 9.8 Critical and says it is remotely exploitable.

### Source excerpt

CVE ID :CVE-2026-109516 Published : Oct. 29, 2026, 3:39 a.m. | 38 minutes ago Description :The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 1.3.0. The `/wp-json/woo-telegram/v1/main/` REST endpoint is registered with `permission_callback => '__return_true'` and performs no Telegram webhook signature verification, allowing an unauthenticated attacker to POST a forged bot update with a `message.chat.id` set to any WordPress login name; `bftow_get_user_system_id()` resolves this attacker-supplied value to the targeted account via `get_user_by('login', $tgId)` with no ownership proof, and writes a login token computed as `md5($_SERVER['HTTP_USER_AGENT'] . time())` -- both inputs are fully attacker-controlled or bounded within seconds using the response's own `Date` header. The resulting token is redeemable at the unauthenticated, capability-check-free, and nonce-less `?action=bftow_create_order&bftow_token=` endpoint, which calls `wp_set_auth_cookie()` unconditionally via `login_user_by_id`, issuing a persistent authenticated session cookie for the targeted account to the attacker. This makes it possible for unauthenticated attackers to log in as any WordPress user, including administrators, given only that user's username. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CodeSOD: Session Recording

DevFeed: [CodeSOD: Session Recording](<https://devfeed.tech/articles/codesod-session-recording-105625.md>)

Original publisher: [Read original article](<https://thedailywtf.com/articles/session-recording>)

Author: Remy Porter

Published: 2026-10-28T06:30:00Z

Content type: article

Language: en

Sources: [The Daily WTF](<https://devfeed.tech/sources/the-daily-wtf.md>)

Topics: [ASP.NET](<https://devfeed.tech/topics/aspnet.md>), [sql-database](<https://devfeed.tech/topics/sql-database.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [asp-net](<https://devfeed.tech/tags/asp-net.md>), [autocomplete](<https://devfeed.tech/tags/autocomplete.md>), [codesod](<https://devfeed.tech/tags/codesod.md>), [database](<https://devfeed.tech/tags/database.md>), [redirect](<https://devfeed.tech/tags/redirect.md>), [sql-injection](<https://devfeed.tech/tags/sql-injection.md>)

### AI overview

The Web Forms snippet reads an album ID from a control, stores it in session, builds and executes a SQL DELETE query using that ID and the session user ID, then redirects. The author criticizes the indirect FindControl-to-Label lookup, using a label to hold input, and the concatenated query as vulnerable to SQL injection. They also question storing the query in a page member and criticize broad use of session state, including for form inputs and loop variables. The redirect's HTTP 300 navigation and the "frm" prefix in the destination URL are additional complaints.

### Source excerpt

We still get a fair bit of old school ASP .Net webforms code, which was cutting edge about twenty years ago, but remains a collection of bad choices that tried to make web programming feel like desktop programming. As an aside, what a reversed world we live in today, where everyone uses Electron and our desktop programming feels like web programming. In any case, Thomas sends us some pretty ugly webforms code. Me.Session("Albumid") = CType(e.Item.FindControl("lblAlbumID"), Label).Text If Not Me.Session("Albumid") Is Nothing And Not Me.Session("Uid") Is Nothing Then Me.strDelSQL = "Delete from tbl_Albumshare_Mast where Album_Id=" & Me.Session("Albumid") & " and Sharer_ID=" & Me.Session("Uid") Me.objDB.ExecQry(Me.strDelSQL) Me.Response.Redirect("frmmyalbumshare.aspx", False) End If Broadly, the goal of this code is to take an album ID from the user and delete an album from the database where the ID matches and the album is owned by this user. And everything is horrible here. First, the use of e.Item.FindControl to look up the input field is suspicious. That's usually what you do when you've dynamically generated controls, but I don't think that's happening here. Because we use FindControl we have to cast it to Label, and only then can we get the text property. That itself raises a question, because why are user inputs getting stored in a label?. That's not what labels are for. They're clearly doing some sort of hacky lookup/autocomplete field thing and using the label to actually store the input, but presenting the user with a different UI for picking it. Not an uncommon pattern in those days, but a hidden field would be a more typical way of doing it. We then construct a SQL injection vulnerability and run it against the database. Then, we use a redirect to send the user to a different page. Again, a common thing to do back then, but a thing I hate: using HTTP 300 codes to redirect users as a form of navigation is awkward and weird. Of course, none of that is precise

## Identity and Access Management Architecture

DevFeed: [Identity and Access Management Architecture](<https://devfeed.tech/articles/identity-and-access-management-architecture-103394.md>)

Original publisher: [Read original article](<https://blog.devops.dev/identity-and-access-management-architecture-ad5dde7e7765?source=rss----33f8b2d9a328---4>)

Author: Scaibu

Published: 2026-10-27T10:20:02Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [saml](<https://devfeed.tech/topics/saml.md>), [WebAuthn](<https://devfeed.tech/topics/webauthn.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [passwords](<https://devfeed.tech/topics/passwords.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [ami](<https://devfeed.tech/tags/ami.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [broker](<https://devfeed.tech/tags/broker.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-and-access](<https://devfeed.tech/tags/identity-and-access.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [login](<https://devfeed.tech/tags/login.md>), [lts](<https://devfeed.tech/tags/lts.md>), [minors](<https://devfeed.tech/tags/minors.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [password](<https://devfeed.tech/tags/password.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [system-design-interview](<https://devfeed.tech/tags/system-design-interview.md>)

### AI overview

Keycloak centralizes login, federation and token issuance, while applications validate signed JWTs locally and retain fine-grained authorization such as tenant roles, API keys and resource permissions. The excerpt recommends coarse roles and identity claims in short-lived tokens, with per-request tenant membership checks and ReBAC in the application. It describes an integration that gets PKCE and five-minute access tokens right but has critical gaps: its JWT verifier decodes tokens without checking signatures, and sign-in and administration still use the legacy password grant. The target design uses Authorization Code with PKCE for people, client credentials for services, device authorization for CLIs, and cached JWKS validation checking signature, issuer, audience and expiry. Keycloak is presented as feature-rich for self-hosted federation and security controls, but requires operating a stateful Java service and keeping pace with quarterly upgrades; it does not replace application-level authorization.

### Source excerpt

A Practical Guide to Authentication, Authorization, Single Sign-On, and Identity FederationWhat Keycloak is? Keycloak is an open-source identity broker and authorization server: it logs users in, issues standards-based tokens, and federates identities from other systems so your services never handle passwords. The current release is 26.8.1, shipped 13 October 2026 (versio.io). It solves three problems at once. Applications delegate login to one place (SSO). Users can come from local accounts, LDAP/AD, or upstream IdPs such as Google or a corporate SAML IdP (brokering and federation). Services verify a signed JWT locally instead of calling a session store on every request. Key facts that shape how you operate it: Lineage. Red Hat has stewarded it since 2018 and ships it commercially as Red Hat build of Keycloak; it is a CNCF incubating project. Runtime. Since version 17 it runs on Quarkus, not WildFly. Old guides using standalone.xml, /auth context paths or jboss-cli are obsolete. No LTS. The community project patches only the latest minor; older lines stop getting security fixes when a new one ships (Skycloak). Minors land roughly quarterly (26.5 Jan, 26.6 Apr, 26.7 Jul, 26.8 Oct 2026), so plan an upgrade cadence, not an install. Admin bootstrap changed. KEYCLOAK_ADMIN / KEYCLOAK_ADMIN_PASSWORD were replaced by KC_BOOTSTRAP_ADMIN_USERNAME / KC_BOOTSTRAP_ADMIN_PASSWORD, which seed a temporary first admin only Core domain model Everything in Keycloak lives inside a realm, a fully isolated namespace with its own users, clients, keys and login policies. The master realm is for administering Keycloak only; never put application users there. Realm. Isolation boundary for users, keys, sessions and flows. Use one realm per trust domain, not per customer; hundreds of realms degrade startup and the admin UX. Client. An application that asks Keycloak to authenticate users or itself. Public clients (SPA, mobile) hold no secret; confidential clients (backends) hold a secret or k

## Mobile Session Architecture: Tokens, Refresh, Device Binding, Logout, and Risk-Based Expiry

DevFeed: [Mobile Session Architecture: Tokens, Refresh, Device Binding, Logout, and Risk-Based Expiry](<https://devfeed.tech/articles/mobile-session-architecture-tokens-refresh-device-binding-logout-and-risk-based-expiry-100957.md>)

Original publisher: [Read original article](<https://proandroiddev.com/mobile-session-architecture-tokens-refresh-device-binding-logout-and-risk-based-expiry-7f7a64de3955?source=rss----c72404660798---4>)

Author: Vaibhav Shakya | Mr Neo

Published: 2026-10-26T23:23:25Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [synchronization](<https://devfeed.tech/topics/synchronization.md>), [App attestation](<https://devfeed.tech/topics/app-attestation.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [audit](<https://devfeed.tech/tags/audit.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [backend](<https://devfeed.tech/tags/backend.md>), [business](<https://devfeed.tech/tags/business.md>), [changes](<https://devfeed.tech/tags/changes.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [detection](<https://devfeed.tech/tags/detection.md>), [device](<https://devfeed.tech/tags/device.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [refresh](<https://devfeed.tech/tags/refresh.md>), [risk](<https://devfeed.tech/tags/risk.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

A mobile session is broader than its tokens: where device management, rapid revocation, replay detection, or risk controls matter, the article recommends server-managed session state tied to a device key, with separate bounded-lifetime access tokens and revocable refresh tokens. It describes rotating refresh tokens as an atomic server-side state transition, coordinated by a single-flight client refresh flow; ambiguous reuse can still reflect retries or races, so response policies should account for them. Cryptographic key binding can protect selected requests, while device-integrity signals should inform risk rather than prove trust. Logout must revoke server state when reachable and clear local credentials, but already issued self-contained access tokens may remain valid until expiry unless services check current state. Idle and absolute expiry, step-up authentication, and risk-based controls should govern sensitive operations. The excerpt also highlights tradeoffs in revocation speed, service availability, and failure handling, and notes that secure storage reduces extraction risk without making a compromised client trustworthy.

### Source excerpt

Authentication in a mobile application is often described as a simple sequence: the user logs in, receives a token, and sends that token with subsequent API requests. That explanation is technically correct but architecturally incomplete. A production mobile session spans several independently changing systems: A mobile application that may remain installed for years An access credential with a deliberately bounded lifetime A longer-lived authorization grant, when refresh capability is issued A device or app-instance identity Server-side session state Account, role, password, and risk changes Multiple API services with different consistency characteristics Logout and revocation events that must propagate across the platform The central architectural mistake is treating the token as the session. A token is only a credential representing part of a session's authority. For systems requiring device management, replay detection, rapid revocation, or risk-based controls, the broader session should be represented by server-managed security state with its own lifecycle, device association, risk state, revocation state, and audit history. Start With a Server-Side Session Model After successful authentication, the backend should create a session record rather than merely issue a pair of tokens. A practical session model might contain: session_id user_id device_key_id refresh_token_family_id current_refresh_token_verifier previous_refresh_token_verifier refresh_generation status created_at last_seen_at idle_expires_at absolute_expires_at risk_level auth_strength revoked_at revocation_reason The mobile application receives: A short-lived access token A longer-lived refresh token A session identifier, directly or indirectly The server's current session-policy metadata The access token is used with resource APIs. The refresh token is sent only to the authorization or session service. It should not be attached to normal business requests. The backend retains enough state to decide

## AppGate gives OT supervisors live monitoring and session termination controls

DevFeed: [AppGate gives OT supervisors live monitoring and session termination controls](<https://devfeed.tech/articles/appgate-gives-ot-supervisors-live-monitoring-and-session-termination-controls-90860.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/10/20/appgate-session-governance/>)

Author: Industry News

Published: 2026-10-20T12:59:32Z

Content type: release

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [zero trust network access](<https://devfeed.tech/topics/zero-trust-network-access.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [audit](<https://devfeed.tech/topics/audit.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [appgate](<https://devfeed.tech/tags/appgate.md>), [audits](<https://devfeed.tech/tags/audits.md>), [builds](<https://devfeed.tech/tags/builds.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [critical](<https://devfeed.tech/tags/critical.md>), [critical-infrastructure](<https://devfeed.tech/tags/critical-infrastructure.md>), [gives](<https://devfeed.tech/tags/gives.md>), [governance](<https://devfeed.tech/tags/governance.md>), [help](<https://devfeed.tech/tags/help.md>), [industry-news](<https://devfeed.tech/tags/industry-news.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [introduced](<https://devfeed.tech/tags/introduced.md>), [live](<https://devfeed.tech/tags/live.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [operational](<https://devfeed.tech/tags/operational.md>), [operational-technology](<https://devfeed.tech/tags/operational-technology.md>), [ot](<https://devfeed.tech/tags/ot.md>), [party](<https://devfeed.tech/tags/party.md>), [reduce](<https://devfeed.tech/tags/reduce.md>)

### AI overview

AppGate's Session Governance extends its ZTNA for OT from controlling who can connect to governing activity during each remote session. It offers session recording, live monitoring, supervisor termination, and vaulted credential injection; asset inventory and groupings can inform access policies. Recording is fail-closed: if it cannot start, the session cannot start. When enabled, its records support assessments against IEC 62443, NERC CIP-005 Interactive Remote Access, NIST SP 800-82, and CMMC. Supervisors retain control over intervention, avoiding reliance on automated remediation that could disrupt physical processes. The system is designed to work with existing monitoring and engineering tools, runs on-premises including in isolated or disconnected networks, and does not depend on cloud round trips. The article describes vendor claims and does not provide independent performance or compliance validation.

### Source excerpt

AppGate has expanded its zero trust offering for operational technology (OT) with Session Governance capabilities that help critical infrastructure operators reduce third-party access risk, simplify compliance audits and protect operational uptime. The expansion builds on the ZTNA for OT offering AppGate introduced in March 2026. The initial release of AppGate ZTNA for OT controlled who could access critical systems. This release governs what happens during each session and gives supervisors the final say when activity ... More -> The post AppGate gives OT supervisors live monitoring and session termination controls appeared first on Help Net Security.

[Next page](<https://devfeed.tech/topics/sessions.md?cursor=WyIyMDI2LTEwLTIwVDEyOjU5OjMyKzAwOjAwIiwgIjc5Mzk0YTg3LWEyMjUtNDdhNC05ZTEzLWViN2IxODQxNjY2NSJd>)