168 matches found
CVE-2026-126280
NocoDB before 2026.08.0 contains a race condition in refresh-token rotation that allows attackers to reuse tokens because UserRefreshToken.ts never checks the affected-row count. Attackers holding a captured refresh token can present it concurrently with the legitimate user to obtain a valid...
CVE-2026-126280
NocoDB before 2026.08.0 contains a race condition in refresh-token rotation that allows attackers to reuse tokens because UserRefreshToken.ts never checks the affected-row count. Attackers holding a captured refresh token can present it concurrently with the legitimate user to obtain a valid...
EUVD-2026-125241
NocoDB before 2026.08.0 contains a race condition in refresh-token rotation that allows attackers to reuse tokens because UserRefreshToken.ts never checks the affected-row count. Attackers holding a captured refresh token can present it concurrently with the legitimate user to obtain a valid...
CVE-2026-126280 NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotation
NocoDB before 2026.08.0 contains a race condition in refresh-token rotation that allows attackers to reuse tokens because UserRefreshToken.ts never checks the affected-row count. Attackers holding a captured refresh token can present it concurrently with the legitimate user to obtain a valid...
CVE-2026-126280
NocoDB versions prior to 2026.08.0 are vulnerable to a race condition in the refresh-token rotation process. The flaw exists because UserRefreshToken.ts fails to verify the affected-row count during rotation. This allows an attacker with a captured refresh token to present it concurrently with a ...
PT-2026-146611
Name of the Vulnerable Software and Affected Versions NocoDB versions prior to 2026.08.0 Description A race condition exists in the refresh-token rotation process. This occurs because the UserRefreshToken.ts file does not verify the affected-row count during the rotation. Consequently, an attacke...
Exploit for CVE-2026-73312
CVE-2026-73312 XenForo before 2.3.13 can leave an OAuth2 refr...
CVE-2026-84203 Memos 0.26.0 through 0.30.0 Insufficient Session Expiration on Password Change
Memos versions 0.26.0 through 0.30.0 fail to revoke refresh tokens when a user changes their password, allowing attackers to maintain account access. An attacker with a stolen refresh token can call the RefreshToken RPC to obtain new access tokens and rotate the refresh token indefinitely,...
CVE-2026-47363
In versions of the Datadog Android application prior to v541-5.9.2, the exported launcher activity AppActivity accepts an attacker-supplied session including OAuth tokens from Intent extras with no permission guard, and signs the app into that session without validating it against the backend. Th...
EUVD-2026-54172
Flowise through 3.1.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint by exploiting prefix-based whitelist matching in the authentication middleware defined in packages/server/src/utils/constants.ts. Attackers...
CVE-2026-70636
Flowise through 3.1.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint by exploiting prefix-based whitelist matching in the authentication middleware defined in packages/server/src/utils/constants.ts. Attackers...
CVE-2026-70636 Flowise 3.1.4 Authentication Bypass via OAuth2 Credential Refresh Endpoint
Flowise through 3.1.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint by exploiting prefix-based whitelist matching in the authentication middleware defined in packages/server/src/utils/constants.ts. Attackers...
CVE-2026-70636
Flowise 3.1.4 contains an authentication bypass affecting the OAuth2 credential refresh endpoint. The root cause is a prefix-based whitelist in the authentication middleware (packages/server/src/utils/constants.ts) that allows an unauthenticated POST to the oauth2-credential refresh route when a ...
PT-2026-68792
Name of the Vulnerable Software and Affected Versions Flowise versions prior to 3.1.5 Description An authentication bypass exists due to prefix-based whitelist matching in the authentication middleware located in packages/server/src/utils/constants.ts. Unauthenticated attackers can send a POST...
Malicious code in @nebula.js/sn-map (npm)
npm/@nebula.js/sn-map is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 the "Shai-Hulud: Here We Go Again" wave — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed versions were trojanized and republished b...
Malicious code in eslint-plugin-folder-schema (npm)
npm/eslint-plugin-folder-schema is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 the "Shai-Hulud: Here We Go Again" wave — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed versions were trojanized and...
Malicious code in @or-sdk/users (npm)
npm/@or-sdk/users is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 the "Shai-Hulud: Here We Go Again" wave — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed versions were trojanized and republished by th...
Malicious code in @servicetitan/react-hooks (npm)
npm/@servicetitan/react-hooks is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 the "Shai-Hulud: Here We Go Again" wave — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed versions were trojanized and...
MAL-2026-11604 Malicious code in @onereach/idw-sdk (npm)
npm/@onereach/idw-sdk is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 the "Shai-Hulud: Here We Go Again" wave — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed versions were trojanized and republished b...
Malicious code in @servicetitan/confirm-navigation (npm)
npm/@servicetitan/confirm-navigation is affected by the large-scale, self-propagating npm supply-chain worm of 2026-08-04 the "Shai-Hulud: Here We Go Again" wave — the same campaign that began with the compromise of the keyv and cacheable maintainer account. The listed versions were trojanized an...