# Authentication

Authentication is the process of proving control of authenticators bound to a subscriber account to demonstrate the subscriber's identity.

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

## HDKEM: Authentication Allocation for Deniable Hybrid Key Exchange

DevFeed: [HDKEM: Authentication Allocation for Deniable Hybrid Key Exchange](<https://devfeed.tech/articles/hdkem-authentication-allocation-for-deniable-hybrid-key-exchange-146008.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.16100>)

Author: Kazi Hassan Shakib, Muhammad Asfand Hafeez, Arslan Munir

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

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

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [hybrid-key-exchange](<https://devfeed.tech/tags/hybrid-key-exchange.md>), [impersonation](<https://devfeed.tech/tags/impersonation.md>), [ml-kem](<https://devfeed.tech/tags/ml-kem.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [post-quantum](<https://devfeed.tech/tags/post-quantum.md>), [quantum-key-distribution](<https://devfeed.tech/tags/quantum-key-distribution.md>), [random](<https://devfeed.tech/tags/random.md>), [ring](<https://devfeed.tech/tags/ring.md>), [secret](<https://devfeed.tech/tags/secret.md>), [split](<https://devfeed.tech/tags/split.md>), [x25519](<https://devfeed.tech/tags/x25519.md>)

### AI overview

HDKEM combines ML-KEM-768, X25519, and an optional pre-shared or QKD-delivered key through a split-key pseudorandom function; the session key remains secret if at least one input stays secure. Its four modes allocate authentication differently: source-backed uses key confirmation under k3, so other holders of k3 can impersonate the server; hide also encrypts the client's signature; mutual adds a server ring signature to prevent that impersonation; and source-less uses ring signatures for both endpoints without k3. The authors report proofs of eCK session-key secrecy in the quantum random-oracle model, explicit authentication, forward secrecy, and session-partner deniability, plus a concrete deniability bound in the classical random-oracle model. With FalconRS, source-backed sends 3,813 bytes in about 26 ms, compared with 5,101 bytes and 47 ms for mutual.

### Source excerpt

arXiv:2610.16100v2 Announce Type: replace Abstract: A deniable authenticated key exchange (DAKE) establishes an authenticated shared key without giving third parties proof of participation. Post-quantum DAKEs use ring signatures, message authentication codes, or split key-encapsulation mechanisms, which differ in who can authenticate and how deniability is achieved. We introduce \emph{authentication allocation} to classify which parties hold secrets that produce accepted authentication messages. For protocols using a fixed two-member ring, we prove that an accuser can simulate a session by either sharing the accused party's authentication key or signing with its own ring key. Thus, deniability relies on key sharing or the ring signature's ability to hide its signer. We propose \HDKEM, combining ML-KEM-768, X25519, and an optional pre-shared or quantum key distribution (QKD)-delivered key $k_3$ through a split-key pseudorandom function. The session key remains secret if at least one input remains secure. Since provisioning services and QKD key managers may know $k_3$, the client always authenticates with its own ring key; the mode determines whether other holders of $k_3$ can impersonate the server. Four modes are supported: \emph{source-backed} authenticates the server through key confirmation under $k_3$, allowing its holders to impersonate the server; \emph{hide} also encrypts the client's signature; \emph{mutual} adds a server ring signature to prevent such impersonation; and \emph{source-less} authenticates both endpoints with ring signatures without $k_3$. We prove extended Canetti--Krawczyk (eCK) session-key secrecy in the quantum random-oracle model, explicit authentication, forward secrecy, and session-partner deniability, with a concrete deniability bound in the classical random-oracle model. With FalconRS, source-backed mode sends 3,813~bytes in about 26~ms, versus 5,101~bytes and 47~ms in mutual mode.

## ASUS Control Center Express Scores CVSS 10.0 for Hard-Coded Cryptographic Key: Attackers Can Gain Administrator Access Without Authentication

DevFeed: [ASUS Control Center Express Scores CVSS 10.0 for Hard-Coded Cryptographic Key: Attackers Can Gain Administrator Access Without Authentication](<https://devfeed.tech/articles/asus-control-center-express-scores-cvss-10-0-for-hard-coded-cryptographic-key-attackers-can-gain-administrator-access-without-authentication-144531.md>)

Original publisher: [Read original article](<https://joho-todai.com/en/asus-control-center-express-critical-vulnerability/>)

Author: Toru Misaki

Published: 2026-11-19T22:24:52Z

Content type: news

Language: en

Sources: [Joho no Todai](<https://devfeed.tech/sources/joho-no-todai.md>)

Topics: [hardcoded credentials](<https://devfeed.tech/topics/hardcoded-credentials.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [ASUS](<https://devfeed.tech/topics/asus.md>)

Tags: [administrator](<https://devfeed.tech/tags/administrator.md>), [allows](<https://devfeed.tech/tags/allows.md>), [asus](<https://devfeed.tech/tags/asus.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-tokens](<https://devfeed.tech/tags/authentication-tokens.md>), [code](<https://devfeed.tech/tags/code.md>), [control-center-express](<https://devfeed.tech/tags/control-center-express.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114202](<https://devfeed.tech/tags/cve-2026-114202.md>), [cve-2026-114204](<https://devfeed.tech/tags/cve-2026-114204.md>), [cve-2026-114205](<https://devfeed.tech/tags/cve-2026-114205.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-v4-0](<https://devfeed.tech/tags/cvss-v4-0.md>), [forge](<https://devfeed.tech/tags/forge.md>), [key](<https://devfeed.tech/tags/key.md>), [management](<https://devfeed.tech/tags/management.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

ASUS Control Center Express has a remotely exploitable hard-coded key flaw, CVE-2026-114202 (CVSS v4.0 10.0), that lets an unauthenticated attacker forge tokens and gain administrator access to the management console. The excerpt also reports two Critical flaws with more restrictive prerequisites: CVE-2026-114204 requires low privileges and a recent login; CVE-2026-114205 requires a low-privileged account to create an administrator account. ASUS directs users to update the console to v1.7.29 and then update and verify agents on managed devices. The advisory says versions before v1.7.29 are affected, while CVE records list versions through v1.7.27, leaving v1.7.28's status unclear; the excerpt recommends v1.7.29 as the safer choice. It also notes separate vulnerabilities in higher-tier Control Center products and Armoury Crate, with distinct access requirements.

### Source excerpt

ASUS Control Center Express contains a hard-coded cryptographic key vulnerability rated the maximum 10.0 under CVSS v4.0. An unauthenticated attacker can gain administrator access, affecting every PC under management. Immediate updating to v1.7.29 is required.

## ASUS warns of critical hard-coded key flaw in Control Center Express

DevFeed: [ASUS warns of critical hard-coded key flaw in Control Center Express](<https://devfeed.tech/articles/asus-warns-of-critical-hard-coded-key-flaw-in-control-center-express-144371.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/asus-warns-of-critical-hard-coded-key-flaw-in-control-center-express/>)

Author: Bill Toulas

Published: 2026-11-19T21:15:59Z

Content type: news

Language: en

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

Topics: [ASUS](<https://devfeed.tech/topics/asus.md>), [hardcoded credentials](<https://devfeed.tech/topics/hardcoded-credentials.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [rbac](<https://devfeed.tech/topics/rbac.md>)

Tags: [administrator](<https://devfeed.tech/tags/administrator.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [armoury-crate](<https://devfeed.tech/tags/armoury-crate.md>), [asus](<https://devfeed.tech/tags/asus.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [business](<https://devfeed.tech/tags/business.md>), [central](<https://devfeed.tech/tags/central.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>), [control-center-express](<https://devfeed.tech/tags/control-center-express.md>), [critical](<https://devfeed.tech/tags/critical.md>), [critical-vulnerabilities](<https://devfeed.tech/tags/critical-vulnerabilities.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-112115](<https://devfeed.tech/tags/cve-2026-112115.md>), [cve-2026-114202](<https://devfeed.tech/tags/cve-2026-114202.md>), [devices](<https://devfeed.tech/tags/devices.md>), [hardcoded-key](<https://devfeed.tech/tags/hardcoded-key.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [it](<https://devfeed.tech/tags/it.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>), [management](<https://devfeed.tech/tags/management.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-monitoring-and-management](<https://devfeed.tech/tags/remote-monitoring-and-management.md>), [security](<https://devfeed.tech/tags/security.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>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

ASUS Control Center Express v1.7.29 fixes three critical flaws that could enable administrative control of the management console or managed devices. CVE-2026-114202 (CVSS 10.0) is the most severe: an unauthenticated remote attacker can forge an authentication token and gain administrator privileges without user interaction. CVE-2026-114204 requires low privileges and a recently logged-in account; CVE-2026-114205 requires a low-privileged account to create an administrator account. ASUS says versions before v1.7.29 are affected, while CVE records list versions through v1.7.27, leaving v1.7.28 unclear. ASUS advises installing v1.7.29, updating managed-device agents through Select Function -> Client Agent Updater, and verifying their versions.

### Source excerpt

ASUS released Control Center Express v1.7.29 to fix three critical vulnerabilities that could let remote attackers gain administrative control of the management console and the devices it manages. [...]

## Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT

DevFeed: [Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT](<https://devfeed.tech/articles/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt-144197.md>)

Original publisher: [Read original article](<https://www.securityweek.com/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt/>)

Author: Eduard Kovacs

Published: 2026-11-19T19:21:06Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [bug](<https://devfeed.tech/topics/bug.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [apt](<https://devfeed.tech/tags/apt.md>), [armory-castle](<https://devfeed.tech/tags/armory-castle.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [backdoors](<https://devfeed.tech/tags/backdoors.md>), [beyondtrust](<https://devfeed.tech/tags/beyondtrust.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [bug](<https://devfeed.tech/tags/bug.md>), [china](<https://devfeed.tech/tags/china.md>), [china-apt](<https://devfeed.tech/tags/china-apt.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [critical](<https://devfeed.tech/tags/critical.md>), [espionage](<https://devfeed.tech/tags/espionage.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [featured](<https://devfeed.tech/tags/featured.md>), [google](<https://devfeed.tech/tags/google.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patched](<https://devfeed.tech/tags/patched.md>), [vcenter](<https://devfeed.tech/tags/vcenter.md>), [vcenter-server](<https://devfeed.tech/tags/vcenter-server.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [vmware-vcenter](<https://devfeed.tech/tags/vmware-vcenter.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [warp-panda](<https://devfeed.tech/tags/warp-panda.md>), [zero-day](<https://devfeed.tech/tags/zero-day.md>)

### AI overview

Google says the China-linked group Armory Castle exploited CVE-2026-123890 in VMware vCenter for more than two months before Broadcom patched it. The unauthenticated flaw could grant administrator access. Mandiant says the attackers first entered through a BeyondTrust Remote Support zero-day, then used the custom tool Bonesaw to steal vCenter's LMDB and SAML signing material, create an SSO administrator account, deploy backdoors, and access an ESXi host. Broadcom fixed the flaw in vCenter 9.1.1.0200, 9.0.2.0200, and 8.0 U3m; no public patch is available for version 7.0, which is out of general support. Mandiant recommends applying patches and checking systems for compromise.

### Source excerpt

Google says a China-linked espionage group exploited a critical VMware vCenter authentication bypass before Broadcom released a patch. The post Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT appeared first on SecurityWeek.

## CVE-2026-77338 - Sprout Track: Authentication bypass via default JWT signing secret

DevFeed: [CVE-2026-77338 - Sprout Track: Authentication bypass via default JWT signing secret](<https://devfeed.tech/articles/cve-2026-77338-sprout-track-authentication-bypass-via-default-jwt-signing-secret-143945.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-19T17:18:59Z

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>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [administrator](<https://devfeed.tech/tags/administrator.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-77338](<https://devfeed.tech/tags/cve-2026-77338.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [network](<https://devfeed.tech/tags/network.md>), [oak-and-sprout](<https://devfeed.tech/tags/oak-and-sprout.md>), [secret](<https://devfeed.tech/tags/secret.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [signing](<https://devfeed.tech/tags/signing.md>), [sprout](<https://devfeed.tech/tags/sprout.md>), [sprout-track](<https://devfeed.tech/tags/sprout-track.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Before version 1.3.5, Sprout Track may use a publicly known JWT signing secret if JWT_SECRET is unset; standard setup does not create a unique one. On a network-reachable affected deployment, an unauthenticated attacker can forge tokens with arbitrary claims, including administrator claims, to access administrative functions and read or modify family, child activity, account, and email data. Deployments configured with a strong unique JWT_SECRET are not affected. The issue is fixed in version 1.3.5; managed and hosted instances were reported remediated.

### Source excerpt

CVE ID :CVE-2026-77338 Published : Nov. 19, 2026, 5:18 p.m. | 26 minutes ago Description :Sprout Track is a self-hosted baby tracking application. Prior to 1.3.5, Sprout Track uses a publicly known hardcoded signing secret when JWT_SECRET is unset, and standard setup does not generate a unique secret. On a network-reachable affected deployment, an unauthenticated attacker can sign JWTs with arbitrary claims, including system-administrator claims, to access administrative functionality and read or modify family, child activity, account, and email data. Deployments with a strong unique JWT_SECRET are not affected. Managed and hosted instances were reported remediated. This issue is fixed in version 1.3.5. Severity: 9.3 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication

DevFeed: [Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication](<https://devfeed.tech/articles/critical-vmware-vcenter-flaw-cvss-9-8-lets-network-attackers-bypass-authentication-143878.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/11/critical-vmware-vcenter-flaw-cvss-98.html>)

Author: The Hacker News

Published: 2026-11-19T15:11:06Z

Content type: news

Language: en

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

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

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [article](<https://devfeed.tech/tags/article.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123890](<https://devfeed.tech/tags/cve-2026-123890.md>), [cve-2026-123891](<https://devfeed.tech/tags/cve-2026-123891.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [enterprise-security](<https://devfeed.tech/tags/enterprise-security.md>), [lets](<https://devfeed.tech/tags/lets.md>), [minutes](<https://devfeed.tech/tags/minutes.md>), [network](<https://devfeed.tech/tags/network.md>), [patch-management](<https://devfeed.tech/tags/patch-management.md>), [system](<https://devfeed.tech/tags/system.md>), [this](<https://devfeed.tech/tags/this.md>), [vcenter](<https://devfeed.tech/tags/vcenter.md>), [virtualization-security](<https://devfeed.tech/tags/virtualization-security.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [vmware-vcenter](<https://devfeed.tech/tags/vmware-vcenter.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Broadcom says CVE-2026-123890 is a CVSS 9.8 authentication bypass in VMware Directory Service that can let a network attacker gain unauthorized access to vCenter. Fixed updates are available for supported branches; Broadcom lists no workaround and calls the issue an emergency change. The flaw affects vCenter 8.0, 9.0, and 9.1 and specified VMware Cloud Foundation, vSphere Foundation, and Telco Cloud builds, including Cloud Foundation 5.x. Enhanced Linked Mode does not affect exposure; older unsupported versions should be presumed affected. Updates are cumulative and cannot be installed with vCenter Quick Patch. VMs keep running during installation, but management access briefly drops and some Standard Key Provider encryption operations pause. Broadcom reports no attacks or public exploit code and does not specify the access gained after bypass. The excerpt also notes an upgrade conflict involving vCenter 8.0 U3m or 9.0.2.0200 and VCF 9.1.1, with options to update vCenter to 9.1.1 first or wait for VCF 9.1.2.

### Source excerpt

Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication A critical flaw in VMware vCenter lets an attacker with network access bypass authentication and gain unauthorized access to the system, Broadcom, which owns VMware, said in an advisory published toda ... Read more Published Date: Nov 19, 2026 (2 hours, 11 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-123894 CVE-2026-123893 CVE-2026-123892 CVE-2026-123891 CVE-2026-123890 CVE-2026-118383 CVE-2026-59310 CVE-2026-59309

## Step-up authentication: how to right-size authentication to risk

DevFeed: [Step-up authentication: how to right-size authentication to risk](<https://devfeed.tech/articles/step-up-authentication-how-to-right-size-authentication-to-risk-142070.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/step-up-authentication-how-to-right-size-authentication-to-risk/>)

Author: Abrom Douglas

Published: 2026-11-18T23:49:07Z

Content type: article

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Amazon Cognito](<https://devfeed.tech/topics/amazon-cognito.md>), [MFA](<https://devfeed.tech/topics/mfa.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.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>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [account-balance](<https://devfeed.tech/tags/account-balance.md>), [acr](<https://devfeed.tech/tags/acr.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-cognito](<https://devfeed.tech/tags/amazon-cognito.md>), [amr](<https://devfeed.tech/tags/amr.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [balance](<https://devfeed.tech/tags/balance.md>), [banking](<https://devfeed.tech/tags/banking.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [identity](<https://devfeed.tech/tags/identity.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [risk](<https://devfeed.tech/tags/risk.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [step-up-authentication](<https://devfeed.tech/tags/step-up-authentication.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [user](<https://devfeed.tech/tags/user.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Amazon Cognito step-up authentication lets applications match authentication strength and freshness to the risk of an action. The app requests a target level with OIDC `acr_values` and optional `max_age`, or `TARGET_ACR_VALUES` and `MAX_AGE` in the `USER_AUTH` API flow. Cognito reports the achieved level and factors in `acr` and `amr`; `auth_time` tracks interactive authentication, while token refresh preserves assurance and does not reset freshness. The application remains responsible for choosing required levels, validating returned claims, and enforcing access. Four patterns cover transaction-level checks, differing requirements across apps sharing SSO, API or SDK sign-in, and federated OIDC providers that map external assurance values. Step-up requires the Essentials or Plus plan; on lower tiers, API requests raise `FeatureUnavailableInTierException`, while managed login ignores `acr_values` and proceeds with normal authentication.

### Source excerpt

Not every action a user takes in an application carries the same risk. Viewing an account balance in a banking application isn't the same as wiring several thousand dollars to a new payee. In practice, though, many applications ask users to prove their identity once at sign-in and then treat every action the same from [...]

## CVE-2026-132144 - MISP: Non-admin users can change login email under external authentication to capture a directory identity

DevFeed: [CVE-2026-132144 - MISP: Non-admin users can change login email under external authentication to capture a directory identity](<https://devfeed.tech/articles/cve-2026-132144-misp-non-admin-users-can-change-login-email-under-external-authentication-to-capture-a-directory-identity-141183.md>)

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

Author: CVEFEED.io

Published: 2026-11-18T20:41:10Z

Content type: news

Language: en

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

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [LDAP](<https://devfeed.tech/topics/ldap.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [backend](<https://devfeed.tech/tags/backend.md>), [capture](<https://devfeed.tech/tags/capture.md>), [change](<https://devfeed.tech/tags/change.md>), [cve-2026-132144](<https://devfeed.tech/tags/cve-2026-132144.md>), [directory](<https://devfeed.tech/tags/directory.md>), [email](<https://devfeed.tech/tags/email.md>), [email-address](<https://devfeed.tech/tags/email-address.md>), [external](<https://devfeed.tech/tags/external.md>), [identity](<https://devfeed.tech/tags/identity.md>), [impact](<https://devfeed.tech/tags/impact.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [logic](<https://devfeed.tech/tags/logic.md>), [login](<https://devfeed.tech/tags/login.md>), [misp](<https://devfeed.tech/tags/misp.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

In MISP installations using LDAP, Shibboleth, ApacheSecureAuth, or CustomAuth, an authenticated non-admin user--including an organization admin--can change their login email to one associated with a higher-privilege directory account. Because the external backend uses that email to resolve identity, organization, and role at login, the next login can assume the matched account's MISP privileges. The reported cause is that UsersController's __canChangeLogin() checks the login-change setting and site-admin status but not whether external authentication is active. Exploitation requires a valid API key or session token and an active external backend; impact is limited to the captured identity's MISP privileges.

### Source excerpt

CVE ID :CVE-2026-132144 Published : Nov. 18, 2026, 8:41 p.m. | 12 minutes ago Description :MISP contains an authorization flaw in the user login-email change logic. When an external authentication backend is configured (LDAP, Shibboleth, ApacheSecureAuth, or CustomAuth), the login email address serves as the key by which the directory service resolves a user's identity, organization, and role on each login. The __canChangeLogin() method in UsersController only checked the MISP.disable_user_login_change setting and site-admin status; it did not account for whether an external authentication backend was active. As a result, any authenticated non-admin user (including org admins) could change their own login email to an address that matches a higher-privilege account in the external directory. On the user's next login, the external backend would resolve that email to the target directory identity, granting the attacker the organization and role associated with that identity. This constitutes an account-identity capture and privilege escalation: the attacker effectively assumes the identity of any directory account whose email they can guess or discover. The vulnerability requires an authenticated session with a valid API key or session token and a MISP instance configured with at least one external authentication backend. The impact is limited to the scope of the captured directory identity's privileges within MISP. Severity: 8.3 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-110009 - Unzer Payments \<= 2.2.1 - Unauthenticated Authentication Bypass to Account Takeover via 'paymentData.email' Parameter

DevFeed: [CVE-2026-110009 - Unzer Payments \<= 2.2.1 - Unauthenticated Authentication Bypass to Account Takeover via 'paymentData.email' Parameter](<https://devfeed.tech/articles/cve-2026-110009-unzer-payments-2-2-1-unauthenticated-authentication-bypass-to-account-takeover-via-paymentdata-email-parameter-140662.md>)

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

Author: CVEFEED.io; wordfence.com

Published: 2026-11-18T14:17:25Z

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>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [account-takeover](<https://devfeed.tech/tags/account-takeover.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [checkout](<https://devfeed.tech/tags/checkout.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-110009](<https://devfeed.tech/tags/cve-2026-110009.md>), [email](<https://devfeed.tech/tags/email.md>), [enumeration](<https://devfeed.tech/tags/enumeration.md>), [google-pay](<https://devfeed.tech/tags/google-pay.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [session](<https://devfeed.tech/tags/session.md>), [unzer-payments](<https://devfeed.tech/tags/unzer-payments.md>), [unzerplugins](<https://devfeed.tech/tags/unzerplugins.md>), [up](<https://devfeed.tech/tags/up.md>), [wordpress](<https://devfeed.tech/tags/wordpress.md>)

### AI overview

Unzer Payments for WordPress versions up to and including 2.2.1 has a critical authentication bypass in its Google Pay Express Checkout endpoint. The handler accepts a submitted `paymentData.email`, finds a matching WordPress user, and issues that account an authenticated session without verifying email ownership, credentials, a nonce, an authentication token, or payment-provider proof. An unauthenticated attacker who knows a user's email could therefore access that account, including an administrator account, potentially taking over the site. The excerpt says the endpoint lacks capability checks, nonce validation, and payment-provider signature verification; it also notes that administrator emails may be discoverable through user enumeration and public site information.

### Source excerpt

CVE ID :CVE-2026-110009 Published : Nov. 18, 2026, 2:17 p.m. | 9 minutes ago Description :The Unzer Payments plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 2.2.1. The vulnerability exists because the Google Pay Express Checkout endpoint (`/?wc-api=google_pay_express`), handled by `startCheckoutDataWithNormalizedCustomerData`, accepts an attacker-controlled `paymentData.email` value and passes it to `createOrGetGuestCustomer()`, which resolves the submitted email to any existing WordPress user via `get_user_by('email', ...)` and then calls `wp_set_current_user()` and `wp_set_auth_cookie()` for the resolved user ID without verifying ownership of the email address, a password, a nonce, an authentication token, or any proof of payment from the payment provider. This makes it possible for unauthenticated attackers to log in as any existing WordPress user -- including administrators -- by submitting that user's known email address, receiving valid `wordpress_logged_in_*` session cookies for the targeted account and achieving full site takeover. The endpoint is entirely unprotected with no capability check, nonce validation, or payment-provider signature verification applied, and administrator email addresses are frequently discoverable via the WordPress REST API user enumeration endpoint (`/wp-json/wp/v2/users`), author archive pages, Gravatar lookups, or site contact footers. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-109857 - Authentication Bypass in CAST Imaging

DevFeed: [CVE-2026-109857 - Authentication Bypass in CAST Imaging](<https://devfeed.tech/articles/cve-2026-109857-authentication-bypass-in-cast-imaging-140658.md>)

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

Author: cvefeed.io

Published: 2026-11-18T13:17:23Z

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>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>)

Tags: [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [cast](<https://devfeed.tech/tags/cast.md>), [cast-software](<https://devfeed.tech/tags/cast-software.md>), [cve-2026-109857](<https://devfeed.tech/tags/cve-2026-109857.md>), [imaging](<https://devfeed.tech/tags/imaging.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>)

### AI overview

CAST Imaging has a critical authentication bypass (CVSS 9.2): its TenantFilter dynamically registers an OpenID Connect issuer from the X-ISSUER-LOCATION HTTP header. An unauthenticated remote attacker can register a malicious identity provider, create accounts matching existing administrator usernames, and obtain JWTs the application accepts, gaining administrative access. The issue is confirmed in version 3.6.2 and may affect other versions; the vendor says it is fixed in newer versions but provides no affected version range.

### Source excerpt

CVE ID :CVE-2026-109857 Published : Nov. 18, 2026, 1:17 p.m. | 1 hour, 9 minutes ago Description :CAST Imaging is vulnerable to authentication bypass in the TenantFilter class. The TenantFilter processes the X-ISSUER-LOCATION HTTP header and dynamically registers an OpenID Connect issuer based on its value. An unauthenticated remote attacker can register a malicious identity provider, create users matching existing administrative usernames, and obtain valid JWTs which will be accepted by the application. This results in complete authentication bypass and privilege escalation to administrative access. The vulnerability has only been confirmed in version 3.6.2 but may also affect other versions. The vendor did not provide the affected version range, but assured that the vulnerability is fixed "in newer versions". Severity: 9.2 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-130747 - Grav before 1.7.53.7 and 2.x before 2.2.18 Authentication Bypass via First-Run Setup

DevFeed: [CVE-2026-130747 - Grav before 1.7.53.7 and 2.x before 2.2.18 Authentication Bypass via First-Run Setup](<https://devfeed.tech/articles/cve-2026-130747-grav-before-1-7-53-7-and-2-x-before-2-2-18-authentication-bypass-via-first-run-setup-140433.md>)

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

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-18T11:34:02Z

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>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-130747](<https://devfeed.tech/tags/cve-2026-130747.md>), [getgrav](<https://devfeed.tech/tags/getgrav.md>), [grav](<https://devfeed.tech/tags/grav.md>), [setup](<https://devfeed.tech/tags/setup.md>)

### AI overview

Grav versions before 1.7.53.7 and 2.x before 2.2.18 are vulnerable to an authentication bypass during first-run setup. When the installation path contains brackets or a backslash, UserCollection::count() uses an unescaped glob() pattern and reports zero users. An anonymous attacker can then use POST /api/v1/auth/setup or the classic admin registration form to create or overwrite a super-admin account. The excerpt gives a severity score of 9.2, labeled critical.

### Source excerpt

CVE ID :CVE-2026-130747 Published : Nov. 18, 2026, 11:34 a.m. | 14 minutes ago Description :Grav before 1.7.53.7 and 2.x before 2.2.18 contains an authentication bypass vulnerability that allows anonymous visitors to create super-admin accounts because UserCollection::count() uses an unescaped glob() pattern. On installs whose path contains brackets or a backslash, the account count returns zero, so attackers can send requests to POST /api/v1/auth/setup or the classic admin registration form to create or overwrite administrator accounts. Severity: 9.2 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## ZDI-26-1036: (0Day) (Pwn2Own) United Chargers Grizzl-E Smart 40A Wi-Fi Configuration Server Missing Authentication Vulnerability

DevFeed: [ZDI-26-1036: (0Day) (Pwn2Own) United Chargers Grizzl-E Smart 40A Wi-Fi Configuration Server Missing Authentication Vulnerability](<https://devfeed.tech/articles/zdi-26-1036-0day-pwn2own-united-chargers-grizzl-e-smart-40a-wi-fi-configuration-server-missing-authentication-vulnerability-142419.md>)

Original publisher: [Read original article](<http://www.zerodayinitiative.com/advisories/ZDI-26-1036/>)

Published: 2026-11-18T06:00:00Z

Content type: news

Language: en

Sources: [Zero Day Initiative](<https://devfeed.tech/sources/zero-day-initiative.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [configuration](<https://devfeed.tech/topics/configuration.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [ev](<https://devfeed.tech/tags/ev.md>), [pwn2own](<https://devfeed.tech/tags/pwn2own.md>), [server](<https://devfeed.tech/tags/server.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [wi-fi](<https://devfeed.tech/tags/wi-fi.md>)

### AI overview

Network-adjacent attackers can modify Wi-Fi settings on affected United Chargers Grizzl-E Smart 40A EV chargers without authentication, due to missing checks on Wi-Fi configuration requests. The advisory says this flaw can be combined with other vulnerabilities to execute arbitrary code in the device's context; it does not describe those other vulnerabilities. ZDI rates it CVSS 6.3 and identifies CVE-2026-131808. The stated mitigation is to restrict interaction with the product. ZDI reports repeated unsuccessful attempts to establish a vendor disclosure channel since April 14, 2026, and lists public release on November 18, 2026.

### Source excerpt

This vulnerability allows network-adjacent attackers to modify Wi-Fi configuration on affected installations of United Chargers Grizzl-E Smart 40A EV chargers. Authentication is not required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 6.3. The following CVEs are assigned: CVE-2026-131808.

## ZDI-26-1037: (0Day) (Pwn2Own) United Chargers Grizzl-E Smart 40A OCPP Backend Configuration Authentication Bypass Vulnerability

DevFeed: [ZDI-26-1037: (0Day) (Pwn2Own) United Chargers Grizzl-E Smart 40A OCPP Backend Configuration Authentication Bypass Vulnerability](<https://devfeed.tech/articles/zdi-26-1037-0day-pwn2own-united-chargers-grizzl-e-smart-40a-ocpp-backend-configuration-authentication-bypass-vulnerability-142420.md>)

Original publisher: [Read original article](<http://www.zerodayinitiative.com/advisories/ZDI-26-1037/>)

Published: 2026-11-18T06:00:00Z

Content type: news

Language: en

Sources: [Zero Day Initiative](<https://devfeed.tech/sources/zero-day-initiative.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [smartdevices](<https://devfeed.tech/topics/smartdevices.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [backend](<https://devfeed.tech/tags/backend.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [pwn2own](<https://devfeed.tech/tags/pwn2own.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

The United Chargers Grizzl-E Smart 40A has an authentication bypass in handling OCPP backend configuration requests. The flaw can be exploited by network-adjacent attackers without authentication; combined with other vulnerabilities, it may allow arbitrary code execution in the device's context. ZDI rates it CVSS 7.6 and lists CVE-2026-131809. ZDI says it made repeated attempts to contact United Chargers without response. Its stated mitigation is to restrict interaction with the product.

### Source excerpt

This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of United Chargers Grizzl-E Smart 40A EV chargers. Authentication is not required to exploit this vulnerability. The ZDI has assigned a CVSS rating of 7.6. The following CVEs are assigned: CVE-2026-131809.

## CVE-2026-116643 - SSH certificate authentication bypass in GitHub Enterprise Server

DevFeed: [CVE-2026-116643 - SSH certificate authentication bypass in GitHub Enterprise Server](<https://devfeed.tech/articles/cve-2026-116643-ssh-certificate-authentication-bypass-in-github-enterprise-server-139504.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-18T02:17:40Z

Content type: news

Language: en

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

Topics: [ssh](<https://devfeed.tech/topics/ssh.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [certificate-authority](<https://devfeed.tech/tags/certificate-authority.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-116643](<https://devfeed.tech/tags/cve-2026-116643.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-server](<https://devfeed.tech/tags/enterprise-server.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [github](<https://devfeed.tech/tags/github.md>), [github-enterprise](<https://devfeed.tech/tags/github-enterprise.md>), [github-enterprise-server](<https://devfeed.tech/tags/github-enterprise-server.md>), [organization](<https://devfeed.tech/tags/organization.md>), [private](<https://devfeed.tech/tags/private.md>), [releases](<https://devfeed.tech/tags/releases.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [required](<https://devfeed.tech/tags/required.md>), [ssh](<https://devfeed.tech/tags/ssh.md>)

### AI overview

CVE-2026-116643 allowed an authenticated GitHub Enterprise Server organization member to read and modify other users' private repositories within a trusted SSH certificate authority's scope. Exploitation required built-in authentication and a valid certificate issued to the attacker by a trusted authority. Supported releases before 3.23 were affected; fixes are available in 3.19.16, 3.20.12, 3.21.10, and 3.22.5. The reported severity is 8.6 (High).

### Source excerpt

CVE ID :CVE-2026-116643 Published : Nov. 18, 2026, 2:17 a.m. | 1 hour, 47 minutes ago Description :An SSH certificate authentication bypass vulnerability in GitHub Enterprise Server allowed an authenticated organization member to read and modify another user's private repositories within the trusted certificate authority's scope. Exploitation required an instance using built-in authentication and a valid certificate issued to the attacker by a trusted SSH certificate authority. This vulnerability affected supported GitHub Enterprise Server releases prior to 3.23 and was fixed in versions 3.19.16, 3.20.12, 3.21.10, and 3.22.5. This vulnerability was reported via the GitHub Bug Bounty program. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-130860 - Flagr before 1.2.5 Authentication Bypass via Default Basic-Auth Whitelist

DevFeed: [CVE-2026-130860 - Flagr before 1.2.5 Authentication Bypass via Default Basic-Auth Whitelist](<https://devfeed.tech/articles/cve-2026-130860-flagr-before-1-2-5-authentication-bypass-via-default-basic-auth-whitelist-138484.md>)

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

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-17T20:17:51Z

Content type: news

Language: en

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

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

Tags: [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [basic](<https://devfeed.tech/tags/basic.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [config](<https://devfeed.tech/tags/config.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-130860](<https://devfeed.tech/tags/cve-2026-130860.md>), [distributions](<https://devfeed.tech/tags/distributions.md>), [flag](<https://devfeed.tech/tags/flag.md>), [flagr](<https://devfeed.tech/tags/flagr.md>), [http](<https://devfeed.tech/tags/http.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [openflagr](<https://devfeed.tech/tags/openflagr.md>), [remote](<https://devfeed.tech/tags/remote.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Flagr versions before 1.2.5 have an authentication bypass in the default FLAGR_BASIC_AUTH_WHITELIST_PATHS setting, which includes /api/v1/flags. The basicAuth.whitelist() middleware matches path prefixes without checking HTTP method, allowing unauthenticated remote attackers to reach flag-management write operations. The stated impact includes creating, modifying, enabling, disabling, and deleting flags and related variants, segments, constraints, and distributions. The excerpt does not provide remediation details.

### Source excerpt

CVE ID :CVE-2026-130860 Published : Nov. 17, 2026, 8:17 p.m. | 47 minutes ago Description :Flagr before 1.2.5 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to access the flag management write API through an insecure default FLAGR_BASIC_AUTH_WHITELIST_PATHS including /api/v1/flags. Because basicAuth.whitelist() in pkg/config/middleware.go matches only path prefixes regardless of HTTP method, attackers can create, modify, enable, disable, and delete flags, variants, segments, constraints, and distributions. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## GitHub Copilot CLI adds Microsoft Entra sign-in as a preview

DevFeed: [GitHub Copilot CLI adds Microsoft Entra sign-in as a preview](<https://devfeed.tech/articles/github-copilot-cli-adds-microsoft-entra-sign-in-as-a-preview-139397.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-11-17-github-copilot-cli-adds-microsoft-entra-sign-in-as-a-preview>)

Author: Allison

Published: 2026-11-17T18:00:35Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [GitHub Copilot CLI](<https://devfeed.tech/topics/github-copilot-cli.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [billing](<https://devfeed.tech/tags/billing.md>), [business](<https://devfeed.tech/tags/business.md>), [cli](<https://devfeed.tech/tags/cli.md>), [client-apps](<https://devfeed.tech/tags/client-apps.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [github-copilot-cli](<https://devfeed.tech/tags/github-copilot-cli.md>), [github-enterprise](<https://devfeed.tech/tags/github-enterprise.md>), [managed](<https://devfeed.tech/tags/managed.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-entra](<https://devfeed.tech/tags/microsoft-entra.md>), [preview](<https://devfeed.tech/tags/preview.md>), [release](<https://devfeed.tech/tags/release.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

GitHub Copilot CLI adds Microsoft Entra sign-in in public preview, requiring CLI version 1.0.113 or later; Entra authentication is currently supported on Windows and macOS, with Linux support to follow. For enterprises using OIDC with Enterprise Managed Users, silent SSO accesses a linked GitHub account without a separate GitHub sign-in. It requires an assigned Copilot Business or Enterprise license and the organization's Copilot CLI policy; requests use GitHub inference and are governed by the GitHub Copilot plan. This SSO option is limited to CLI and VS Code. For Frontier organizations with a Microsoft 365 Copilot license and usage-based billing, sign-in can provide terminal access to Microsoft Copilot models without a GitHub account. That path uses Microsoft 365 inference, with model access and limits managed in Microsoft 365 Copilot settings. Work IQ MCP can provide Microsoft 365 work data as context. The excerpt says setup steps are in the CLI documentation.

### Source excerpt

GitHub Copilot CLI now supports Microsoft Entra authentication in public preview. You can sign in with your Microsoft Entra account to silently authenticate to a linked GitHub Enterprise Managed User... The post GitHub Copilot CLI adds Microsoft Entra sign-in as a preview appeared first on The GitHub Blog.

## The risks of device code authentication for AI coding agents

DevFeed: [The risks of device code authentication for AI coding agents](<https://devfeed.tech/articles/the-risks-of-device-code-authentication-for-ai-coding-agents-138244.md>)

Original publisher: [Read original article](<https://www.microsoft.com/en-us/security/blog/2026/11/17/the-risks-of-device-code-authentication-for-ai-coding-agents/>)

Author: Microsoft Security Research

Published: 2026-11-17T15:00:00Z

Content type: news

Language: en

Sources: [Microsoft Security](<https://devfeed.tech/sources/microsoft-security-blog.md>)

Topics: [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [GitHub Copilot CLI](<https://devfeed.tech/topics/github-copilot-cli.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [blog](<https://devfeed.tech/tags/blog.md>), [can](<https://devfeed.tech/tags/can.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cli](<https://devfeed.tech/tags/cli.md>), [client](<https://devfeed.tech/tags/client.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [device](<https://devfeed.tech/tags/device.md>), [device-code](<https://devfeed.tech/tags/device-code.md>), [device-code-phishing](<https://devfeed.tech/tags/device-code-phishing.md>), [example](<https://devfeed.tech/tags/example.md>), [flow](<https://devfeed.tech/tags/flow.md>), [github](<https://devfeed.tech/tags/github.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [social-engineering](<https://devfeed.tech/tags/social-engineering.md>), [token-theft](<https://devfeed.tech/tags/token-theft.md>)

### AI overview

In a controlled lab, researchers showed that approving an attacker-started GitHub device-code request could expose a Copilot CLI user's repositories and synced sessions, let misleading memory entries affect later interactions, or enable remote steering of an active session. Each outcome depends on account permissions and enabled features; remote steering also requires an active online session, remote control enabled, and organization policy allowing it. These are proof-of-concept results, not attacks observed in the wild, and the device-flow phishing technique can target any public client that supports the flow. Users should approve only sign-ins they initiated. Organizations can review and revoke unexpected OAuth grants, limit repository access, review session and memory settings, and connect GitHub Enterprise Cloud to Defender for Cloud Apps to support investigations. Detection and disruption capabilities require supported configurations and integrations.

### Source excerpt

Lab research shows how device code phishing, a technique that applies to any device-flow client, can extend to AI coding agents, using GitHub Copilot CLI as an illustrative example. The post The risks of device code authentication for AI coding agents appeared first on Microsoft Security Blog.

## CVE-2026-130591 - 53AIHub before 0.5.5 Missing Authentication via File Preview Endpoints

DevFeed: [CVE-2026-130591 - 53AIHub before 0.5.5 Missing Authentication via File Preview Endpoints](<https://devfeed.tech/articles/cve-2026-130591-53aihub-before-0-5-5-missing-authentication-via-file-preview-endpoints-137896.md>)

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

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-17T14:17:46Z

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>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [file](<https://devfeed.tech/topics/file.md>)

Tags: [53ai](<https://devfeed.tech/tags/53ai.md>), [53aihub](<https://devfeed.tech/tags/53aihub.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cve-2026-130591](<https://devfeed.tech/tags/cve-2026-130591.md>), [file](<https://devfeed.tech/tags/file.md>), [preview](<https://devfeed.tech/tags/preview.md>)

### AI overview

53AIHub versions before 0.5.5 are described as missing authentication on `/api/files/:file_id/preview` and `/api/file-version/:file_body_id`. Unauthenticated attackers can reportedly enumerate sequential numeric IDs to read raw knowledge-base files and stored file versions across enterprise tenants. The excerpt gives a severity score of 8.7; it does not provide remediation details.

### Source excerpt

CVE ID :CVE-2026-130591 Published : Nov. 17, 2026, 2:17 p.m. | 2 hours, 20 minutes ago Description :53AIHub before 0.5.5 contains a missing authentication vulnerability that allows unauthenticated attackers to read files by requesting /api/files/:file_id/preview and /api/file-version/:file_body_id without UserTokenAuth. Attackers can enumerate sequential numeric ids to read raw knowledge-base files and stored file versions belonging to any enterprise tenant. Severity: 8.7 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-120387 - CIRCUTOR PowerStudio SCADA WAVE JWT Signature Validation Authentication Bypass

DevFeed: [CVE-2026-120387 - CIRCUTOR PowerStudio SCADA WAVE JWT Signature Validation Authentication Bypass](<https://devfeed.tech/articles/cve-2026-120387-circutor-powerstudio-scada-wave-jwt-signature-validation-authentication-bypass-136590.md>)

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

Author: CVEFEED.io

Published: 2026-11-17T05:18:33Z

Content type: news

Language: en

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

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

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [component](<https://devfeed.tech/tags/component.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-120387](<https://devfeed.tech/tags/cve-2026-120387.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [functionality](<https://devfeed.tech/tags/functionality.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [jwt-signature-verification](<https://devfeed.tech/tags/jwt-signature-verification.md>), [none](<https://devfeed.tech/tags/none.md>), [remote](<https://devfeed.tech/tags/remote.md>), [scada](<https://devfeed.tech/tags/scada.md>), [token](<https://devfeed.tech/tags/token.md>), [user](<https://devfeed.tech/tags/user.md>), [validation](<https://devfeed.tech/tags/validation.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

CVE-2026-120387 is reported as a critical (10.0) remotely exploitable authentication bypass in the desktop version of CIRCUTOR PowerStudio SCADA WAVE. An unauthenticated attacker can submit an unsigned JWT using the "none" algorithm; the shared validation component reportedly accepts it without checking a cryptographic signature, enabling impersonation and access to protected functionality with the impersonated user's privileges. The excerpt lists no affected product versions, so it does not establish the precise scope.

### Source excerpt

CVE ID :CVE-2026-120387 Published : Nov. 17, 2026, 5:18 a.m. | 1 hour, 4 minutes ago Description :An improper JWT signature verification vulnerability in CIRCUTOR PowerStudio SCADA WAVE desktop version allows an unauthenticated remote attacker to bypass authentication by submitting an unsigned JWT with the algorithm set to "none". The shared JWT validation component accepts the token without verifying a cryptographic signature, allowing the attacker to impersonate another user and access protected functionality with that user's privileges. Severity: 10.0 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Security Authentication as Protective Friction: Understanding the Dual Effects of Authentication Measures in e-Government Platform

DevFeed: [Security Authentication as Protective Friction: Understanding the Dual Effects of Authentication Measures in e-Government Platform](<https://devfeed.tech/articles/security-authentication-as-protective-friction-understanding-the-dual-effects-of-authentication-measures-in-e-government-platform-139275.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.19435>)

Author: Jianshan Pan, Zongyi Chen, Qiyou Lin, Xiaofang Cai

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

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

Tags: [authentication](<https://devfeed.tech/tags/authentication.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-hc](<https://devfeed.tech/tags/cs-hc.md>), [effects](<https://devfeed.tech/tags/effects.md>), [government](<https://devfeed.tech/tags/government.md>), [platform](<https://devfeed.tech/tags/platform.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The authors frame stringent e-government authentication, such as facial recognition and multi-factor verification, as "protective friction": overt, non-elective effort that impedes users while serving security. Their proposed model has two pathways: authentication reduces perceived privacy-security risk but raises effort cost; self-efficacy moderates only the risk pathway. They propose that users' understanding of authentication's protective purpose may matter more than their ability to overcome the effort. This research-in-progress plans to test the model through a survey of platform users and interviews with staff at a Chinese municipal credit center. The supplied abstract describes a proposed study, not empirical findings.

### Source excerpt

arXiv:2611.19435v1 Announce Type: new Abstract: E-Government platforms, such as government credit platforms, handle highly sensitive personal data, requiring stringent security authentication (e.g., facial recognition, multi-factor verification) that protects users but impedes their experience. Drawing on Tomalin's (2023) e-friction typology and the emerging literature on beneficial design friction, we reconceptualize these authentication measures as protective friction, a theoretically distinct form of non-elective, overt, impeding e-friction that serves a security-enhancing function. We propose a dual-pathway model in which protective friction simultaneously reduces privacy-security risk perception (protection pathway) and increases effort cost (cost pathway), with self-efficacy moderating only the risk pathway. This differential pattern suggests that what matters is not users' ability to overcome friction, but their comprehension of its protective purpose, a construct we term protective mechanism comprehension. We outline a mixed-methods research design combining a survey of platform users and semi-structured interviews with platform staff at a Chinese municipal credit center to test this model. This research-in-progress contributes to IS theory by extending e-friction research from conceptual typology to empirical investigation, identifying when security friction becomes beneficial rather than burdensome.

## Agent Authenticator: Passkey-Grade, Hardware-Bound Authentication for AI Agents

DevFeed: [Agent Authenticator: Passkey-Grade, Hardware-Bound Authentication for AI Agents](<https://devfeed.tech/articles/agent-authenticator-passkey-grade-hardware-bound-authentication-for-ai-agents-137457.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.19536>)

Author: Harish Santhanalakshmi Ganesan

Published: 2026-11-17T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Authentication](<https://devfeed.tech/topics/authentication.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [ssh](<https://devfeed.tech/topics/ssh.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [actions](<https://devfeed.tech/tags/actions.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [passkey](<https://devfeed.tech/tags/passkey.md>)

### AI overview

The Agent Authenticator proposes replacing AI agents' readable bearer secrets with per-service hardware-bound keys and runtime-enforced origin binding. Human-signed scoped mandates define permitted actions, with cross-device human approval for high-risk actions; normalized environment attestation and a signed, hash-chained action record provide additional checks and traceability. The same protocol is designed for developer laptops and cloud enclaves, and is framed as a profile over existing mechanisms--including MCP authorization, OAuth token exchange, git, and SSH--rather than a new identity system. The authors analyze it against prompt injection and same-host compromise, relate it to five incidents, and discuss limitations; the supplied excerpt does not provide implementation results or details of those limits.

### Source excerpt

arXiv:2611.19536v1 Announce Type: cross Abstract: AI coding agents now push code, publish packages, call model APIs and operate cloud resources on behalf of developers. They authenticate to these services with the same bearer secrets humans use, personal access tokens, API keys and package-registry tokens, stored where the model, its subprocesses and any co-resident malware can read them. Incidents in 2025 and 2026, including prompt-injection attacks on coding agents and self-propagating supply-chain worms, show that this arrangement fails in predictable ways. Passkeys solved the analogous problem for humans, but they require a human gesture on every use and cannot be operated by an autonomous process. We present the Agent Authenticator, a design that gives agents passkey-grade authentication properties: per-service hardware-bound keys, no shared secrets, origin binding enforced by the runtime rather than the model, normalized attestation of the execution environment, human-signed scoped mandates, and cross-device human approval for high-risk actions. The same protocol serves agents on developer laptops and in cloud enclaves, and it deploys as a profile over existing mechanisms, MCP authorization, OAuth token exchange including the Identity Assertion JWT Authorization Grant, git and SSH, rather than as a new identity system. The authenticator also produces a signed, hash-chained record of each action it authorizes. We analyze the design against a threat model centered on prompt injection and same-host compromise, map it onto five documented incidents, and discuss its limits.

## CVE-2026-104840 - OpenCTI: No rate limiting on authentication endpoint allows credential brute-forcing

DevFeed: [CVE-2026-104840 - OpenCTI: No rate limiting on authentication endpoint allows credential brute-forcing](<https://devfeed.tech/articles/cve-2026-104840-opencti-no-rate-limiting-on-authentication-endpoint-allows-credential-brute-forcing-136266.md>)

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

Author: CVEFEED.io; github.com

Published: 2026-11-16T21:17:17Z

Content type: article

Language: en

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

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [account](<https://devfeed.tech/topics/account.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [citeum](<https://devfeed.tech/tags/citeum.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-104840](<https://devfeed.tech/tags/cve-2026-104840.md>), [cyber-threat-intelligence](<https://devfeed.tech/tags/cyber-threat-intelligence.md>), [express](<https://devfeed.tech/tags/express.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [global](<https://devfeed.tech/tags/global.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [login](<https://devfeed.tech/tags/login.md>), [make](<https://devfeed.tech/tags/make.md>), [network](<https://devfeed.tech/tags/network.md>), [opencti](<https://devfeed.tech/tags/opencti.md>), [opencti-platform](<https://devfeed.tech/tags/opencti-platform.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [threat-intelligence](<https://devfeed.tech/tags/threat-intelligence.md>), [token](<https://devfeed.tech/tags/token.md>), [user](<https://devfeed.tech/tags/user.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Before OpenCTI 7.260428.0, the GraphQL token mutation used for primary login lacked an endpoint-specific rate limit. The global Express limiter allowed up to 10,000 requests per second, enabling unauthenticated remote attackers to guess passwords against a chosen account at network speed. A recovered credential could expose that account's threat-intelligence data and permitted operations. The issue is fixed in version 7.260428.0.

### Source excerpt

CVE ID :CVE-2026-104840 Published : Nov. 16, 2026, 9:17 p.m. | 1 hour, 37 minutes ago Description :OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260428.0, the token GraphQL mutation used for primary login has no endpoint-specific rate limit, while the global Express limiter defaults to permitting 10,000 requests in a one-second window. An unauthenticated remote attacker can make password guesses at network speed against a chosen user account and, if a credential is recovered, access the account's threat-intelligence data and permitted operations. This issue is fixed in version 7.260428.0. Severity: 9.2 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-21167 - Smart Switch Unrestricted IP Binding Authentication Bypass

DevFeed: [CVE-2026-21167 - Smart Switch Unrestricted IP Binding Authentication Bypass](<https://devfeed.tech/articles/cve-2026-21167-smart-switch-unrestricted-ip-binding-authentication-bypass-135351.md>)

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

Author: CVEFEED.io; samsung.com

Published: 2026-11-16T12:17:57Z

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>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [cve-2026-21167](<https://devfeed.tech/tags/cve-2026-21167.md>), [samsung](<https://devfeed.tech/tags/samsung.md>), [smart-switch](<https://devfeed.tech/tags/smart-switch.md>)

### AI overview

Smart Switch versions before 3.7.74.7 have an authentication bypass caused by binding to an unrestricted IP address. The description says an adjacent attacker can exploit it, but user interaction is required. The source rates the vulnerability 8.6 (High); it provides no remediation details or affected-product version list.

### Source excerpt

CVE ID :CVE-2026-21167 Published : Nov. 16, 2026, 12:17 p.m. | 1 hour, 20 minutes ago Description :Binding to an unrestricted IP address in Smart Switch prior to version 3.7.74.7 allows adjacent attackers to bypass authentication. User interaction is required for triggering this vulnerability. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-129552 - Tensei through 0.11.5 Authentication Bypass via Hard-Coded JWT Secret in @tensei/auth

DevFeed: [CVE-2026-129552 - Tensei through 0.11.5 Authentication Bypass via Hard-Coded JWT Secret in @tensei/auth](<https://devfeed.tech/articles/cve-2026-129552-tensei-through-0-11-5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth-135346.md>)

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

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-16T12:17:53Z

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>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-129552](<https://devfeed.tech/tags/cve-2026-129552.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [secret](<https://devfeed.tech/tags/secret.md>)

### AI overview

Tensei through 0.11.5 has an authentication bypass in @tensei/auth when JWT_SECRET is unset: the package falls back to the hard-coded signing key `auth-secret-key`. The supplied description says unauthenticated attackers can sign tokens with arbitrary user IDs that `populateContextFromToken` accepts, allowing impersonation of any user, including administrators. The source rates the issue 9.8 (critical); it does not provide mitigation or remediation steps.

### Source excerpt

CVE ID :CVE-2026-129552 Published : Nov. 16, 2026, 12:17 p.m. | 1 hour, 20 minutes ago Description :Tensei through 0.11.5 contains an authentication bypass vulnerability in @tensei/auth that falls back to the hard-coded JWT signing key 'auth-secret-key' when JWT_SECRET is unset. Unauthenticated attackers can sign tokens with arbitrary user ids accepted by populateContextFromToken to impersonate any user, including administrators. Severity: 9.8 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

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