CVE-2026-129863
GitBucket through 4.48.0 contains an incorrect authorization vulnerability that allows authenticated users to edit and merge other users' pu
CVSS
6.5
Média
EPSS
—
KEV
—
Exploit Today
—
0-100
Publicado: 16 de nov. de 2026 · Última mod.: 16 de nov. de 2026 · CWE-863
Ainda não há histórico EPSS suficiente.
GitBucket through 4.48.0 contains an incorrect authorization vulnerability that allows authenticated users to edit and merge other users' pull requests because the PATCH pulls and PUT pulls merge REST API endpoints only check read access. Attackers can close, reopen, retitle, retarget, or merge pull requests into the base branch without write permission on public repositories or as private-repository guest collaborators.
- github.comhttps://github.com/gitbucket/gitbucket/blob/4.48.0/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala#L155-L173
- github.comhttps://github.com/gitbucket/gitbucket/blob/4.48.0/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala#L229-L270
- github.comhttps://github.com/gitbucket/gitbucket/commit/876c8524967356dfea4a0508c4e1444ad8c80832
- github.comhttps://github.com/gitbucket/gitbucket/issues/4179
- github.comhttps://github.com/gitbucket/gitbucket/pull/4181
- hackmd.iohttps://hackmd.io/@hieund/gitbucket-pr-api-missing-write-authz
- www.vulncheck.comhttps://www.vulncheck.com/advisories/gitbucket-through-4.48.0-incorrect-authorization-via-pull-request-api-endpoints
- hackmd.iohttps://hackmd.io/@hieund/gitbucket-pr-api-missing-write-authz
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-1292396.5 MÉD—
———Directus is a real-time API and App dashboard for managing SQL database content. Prior to 12.3.1, Directus allows an authenticated non-admin with update permission on directus_shares to modify user_created, role, item, and collection on an existing owned share because authorization checks the pre-update row and does not revalidate the merged row. The update path does not force user_created to the acting user or rerun share access checks when item or collection changes. Setting user_created and role to administrator identifiers causes guest share authentication to derive administrator accountability from both fields, exposing data reachable from the shared item beyond the owner and share role permissions. The issue requires update permission on directus_shares, an item the account can share, and knowledge of administrator user and role identifiers, and it does not issue an administrator token or provide write or availability impact. This issue is fixed in version 12.3.1.5hCVE-2026-1298813.7 BAI—
———Weblate 2026.6 through 2026.11.2 contains an information disclosure vulnerability in ChangeManager.last_changes() that exposes workspaces the viewer cannot view by skipping Workspace.can_view() checks site-wide. Anonymous visitors on instances with REQUIRE_LOGIN disabled and only public projects can query /changes/, /api/changes/, or RSS/CSV feeds to obtain hidden workspace names, UUIDs, actions, and timestamps.8hCVE-2026-124631——
——0In affected versions of Octopus Server, insufficient authorization checks allowed a low-privileged authenticated user to register an Argo CD gateway, which could result in unauthorized changes to Argo CD Application data for projects and environments outside their permissions within the same Space.11hCVE-2026-124629——
——0In affected versions of Octopus Server, insufficient authorization checks on scheduled project triggers allowed users who were permitted to deploy existing releases, but not to create new ones, to configure a trigger that could result in new releases being created and deployed without the required permission being assigned. The resulting audit events were attributed to the system rather than to the user who configured the trigger.11hCVE-2026-821568.8 ALT—
——0Dell PowerStore contains an authorization-bypass vulnerability. A low-privileged attacker could exploit it, potentially leading to elevation of privilege to administrator.7hCVE-2026-129341——
——0The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reachable with read access to issues or pull requests. A user who had uploaded a release asset could still delete it after losing write access to the repository. The endpoint now only deletes attachments that the user uploaded and that are not yet linked to an issue, comment or release.1d