CSSA Exclusive Early Warning10.0 Critical
Claude for Chrome extension session non-revocation flaw leading to unauthorized access and quota exhaustion
An attacker can steal access and refresh tokens from local storage through browser profile theft or malware extraction, then maintain session validity by exploiting a logic flaw in which the global logout instruction fails to revoke server-side OAuth authorization at the same time. The technical mechanism is that the client logout flow only clears the local cache without triggering a token revocation request, leaving hidden authorization chains outside the control of the normal session inventory. Affected entities face loss of control over the credential lifecycle, and an attacker can use this to bypass the security boundary and issue unauthorized inference requests, causing sensitive data exposure and unintended consumption of billing quota.
Component
This component is the official browser extension and terminal interaction module of the claude-code ecosystem. Its architecture implements cross-endpo…
Type
Insufficient Session Expiration (CWE-613)
Repo
Remediation- It is recommended to follow the OAuth 2.0 specification and issue a token revocation request to the server whenever the client logs out. A global logout event linkage mechanism should be established so that password resets cascade to terminate all associated authorizations. Authorization records for every endpoint should be presented centrally in the account center, together with a unified remote revocation interface.
CVE-2026-67191CVSS 9.8 Critical2026-07-30
Xlight FTP Server SSH Pre-Authentication Heap Overflow Leading to Remote Code Execution
In Xlight FTP Server prior to version 3.9.5, a logic error in the SSH/SFTP connection handling module results in a heap buffer overflow (CWE-122) security flaw. The recv loop termination condition mistakenly uses an OR operator instead of an AND operator, allowing an attacker to write data past the end of the heap buffer before authentication by sending a malformed SSH client identification string. Xlight FTP Server contains a memory corruption vulnerability when establishing SSH or SFTP connections, which an attacker can trigger with a crafted connection request, leading to remote code execution or service disruption. The vulnerability affects all Xlight FTP Server users who have not updated to 3.9.5. An attacker only needs to initiate a crafted SSH/SFTP connection to the target server to exploit it, requiring no user interaction and allowing remote control.
Component
Xlight FTP Server is FTP and SFTP server software for the Windows platform, supporting file transfer and management.
Risks
- From standard user to administrator: If the victim runs the FTP service with administrative privileges, the attacker gains the same privileges
- Complete system control: An attacker can execute arbitrary code on the victim system, and depending on user privileges, install programs, view/modify/delete data or create new accounts with full privileges
- No user interaction required: Through a remote network attack, an attacker can trigger the vulnerability with no user interaction, exploiting network reachability directly
Source
Remediation- Immediately upgrade Xlight FTP Server to version 3.9.5 or later
- Monitor SSH/SFTP connection logs and identify anomalous client identification strings
- Restrict access to FTP/SFTP ports at the network boundary and allow connections only from trusted IP addresses
CVE-2026-59243CVSS 9.8 Critical2026-07-29
Apache Airflow FAB Azure AD OAuth Signature Verification Bypass Enabling Login as Any User
In apache-airflow-providers-fab prior to version 3.7.3, the FAB auth manager decodes the ID token with verify_signature set to False by default when handling Azure AD OAuth login. This configuration defect results in improper verification of a cryptographic signature (CWE-347): an attacker who can submit a forged or unsigned (alg:none) ID token to the OAuth callback can bypass the authentication mechanism. The vulnerability allows an attacker to log in as any user, including administrator accounts holding the Admin role. Affected are all deployments running the FAB auth manager under the default configuration and using the Azure AD OAuth login path; notably the Authentik path already defaults to True and is therefore not affected by this particular default-configuration flaw. An attacker needs no complex interaction and can achieve remote identity takeover simply by crafting a malicious token.
Component
Apache Airflow is a platform for programmatically authoring, scheduling and monitoring workflows. The FAB (Flask AppBuilder) auth manager is its commonly used authentication component, supporting integration with multiple OAuth providers.
Risks
- From standard user to administrator: An attacker can forge a token and log in directly with the Admin role, gaining the highest system privileges
- Complete system control: Once administrator privileges are obtained, an attacker can execute arbitrary code, view/modify/delete data or create new accounts with full privileges
- No user interaction required: An attacker can trigger the vulnerability by sending a forged OAuth callback request remotely over the network, with no additional interaction from the target user
Source
Remediation- Immediately upgrade apache-airflow-providers-fab to version 3.7.3 or later, which changes the verify_signature default to True
- Review the current deployment configuration and ensure signature verification is explicitly enabled for all OAuth login paths
- Monitor OAuth callback logs to identify and block anomalous unsigned or forged token requests
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
4da10d58965c39c325c7e0e006b64294
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
1a7aea2ffabb4a1ab4c3be812fd4191f
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
e07402d2c4867d9c1092a043dcc488ce
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
ab892acf635c44646d1d4861a4f17265
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
aeac0b7844dc9427533a41b87f95de0d
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
430597910002dd741ec36d4bea561d41
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
229fe3e129814dbd4ce851606ff127e1
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
234c53575e40010e898862d17be1eefc
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
577ffd7eea4eef70066cfeb32774731f
Package Poisoning2026-07-30
@ flagged as malicious
This version was found communicating with a malicious domain and executing malicious commands. Audit your dependencies and pin safe versions immediately.
MD5
f10ea83a42993b6184eb92bf278f3899
