407 matches found
CVE-2025-6554
CVE-2025-6554 function leakhole let x; delete x?.y?.a; return y; let y; function pwn let hole = leakhole; %DebugPrinthole; pwn; Bug A variable y was accessed before declaration. Normally this should trigger a ReferenceError TDZ, but in older V8, when combined with delete x?.y, the check failed an...
CVE-2026-102460
In Eclipse Vert.x versions 4.0.0, 4.5.34 or 5.0.0,5.0.12 or 5.1.0,5.1.9 or 5.2.0, 5.2.0, a scope bypass vulnerability exists in Eclipse Vert.x Web's ChainAuthHandler when used with scope-requiring authentication handlers such as JWTAuthHandler or OAuth2AuthHandler. When a user is already...
EUVD-2026-101605
In Eclipse Vert.x versions 4.0.0, 4.5.34 or 5.0.0,5.0.12 or 5.1.0,5.1.9 or 5.2.0, 5.2.0, a scope bypass vulnerability exists in Eclipse Vert.x Web's ChainAuthHandler when used with scope-requiring authentication handlers such as JWTAuthHandler or OAuth2AuthHandler. When a user is already...
CVE-2026-102460
In Eclipse Vert.x versions 4.0.0, 4.5.34 or 5.0.0,5.0.12 or 5.1.0,5.1.9 or 5.2.0, 5.2.0, a scope bypass vulnerability exists in Eclipse Vert.x Web's ChainAuthHandler when used with scope-requiring authentication handlers such as JWTAuthHandler or OAuth2AuthHandler. When a user is already...
CVE-2026-102460
Eclipse Vert.x Web (Maven coordinate io.vertx:vertx-web ) is vulnerable to a scope bypass in the ChainAuthHandler component. This affects versions [4.0.0, 4.5.34] , [5.0.0, 5.0.12] , [5.1.0, 5.1.9] , and [5.2.0, 5.2.0] . The root cause is that postAuthentication() relies on internal state establi...
CVE-2026-70396
Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories ...
CVE-2026-73126 Gitea private workflow badge token scope bypass
Gitea's Actions workflow status badge endpoint does not enforce repository-read scope or the public-only restriction on the token authenticating the request. A token lacking read:repository, or restricted to public repositories, can retrieve the latest workflow status of a private repository...
CVE-2026-73126
Gitea versions
CVE-2026-73126
Gitea's Actions workflow status badge endpoint does not enforce repository-read scope or the public-only restriction on the token authenticating the request. A token lacking read:repository, or restricted to public repositories, can retrieve the latest workflow status of a private repository...
CVE-2026-70407 Gitea organization listing token scope bypass
Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator's token, the response can include Limited and private organizations, bypassin...
CVE-2026-70407
The Gitea organization-list API (endpoint GET /api/v1/orgs) fails to enforce the read:organization token scope. Consequently, a token with a different category, such as read:misc , can retrieve organization metadata visible to its owner. If the token belongs to a site administrator , the response...
CVE-2026-70407 Gitea organization listing token scope bypass
Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator's token, the response can include Limited and private organizations, bypassin...
CVE-2026-70407
Gitea's organization-list API does not enforce the read:organization token scope. A token limited to another category, such as read:misc, can retrieve organization metadata visible to its owner. For a site administrator's token, the response can include Limited and private organizations, bypassin...
CVE-2026-70396 Gitea organization repository creation token scope bypass
Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories ...
CVE-2026-70396
The Gitea organization repository-creation API (specifically POST /api/v1/orgs/{org}/repos) is vulnerable to a token scope bypass due to incorrect authorization. While the API correctly requires the write:organization scope, it fails to enforce the write:repository scope required by other reposit...
CVE-2026-70396
Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories ...
CVE-2026-70396 Gitea organization repository creation token scope bypass
Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories ...
CVE-2026-109182
jshERP through 3.6 contains an incorrect authorization vulnerability in GET /supplier/exportExcel that allows authenticated users to bypass role data scope restrictions enforced by /supplier/list. Attackers restricted to personal or department data can export every supplier, customer and member...
CVE-2026-109184 jshERP through 3.6 Data Scope Bypass via /account/findAccountInOutList
jshERP through 3.6 contains an improper authorization vulnerability that allows low-privilege authenticated users to read any settlement account ledger by supplying an arbitrary accountId. Attackers restricted to personal or department data scope can query GET /account/findAccountInOutList to vie...
CVE-2026-109182
jshERP versions through 3.6 are affected by an incorrect authorization vulnerability (CWE-863) in the GET /supplier/exportExcel endpoint. While the /supplier/list endpoint correctly enforces role data scope restrictions, this specific export function fails to do so. This allows authenticated user...