GitBucket through 4.48.0 contains an incorrect authorization vulnerability that allows authenticated users to edit and
Source GCVE Database
Not known to be exploited · CVSS 7.1 High.
Data as of 16 Nov 2026, 17:19 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.1 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 6.5 |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GitBucketGitBucket | Affected
| Fixed in– |
GitHubGitBucketpkg:github/GitBucketOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict authenticated user permissions carefully and monitor repository access controls to limit potential exploitation.
Description
GitBucket versions through 4.48.0 have an authorization vulnerability where authenticated users can improperly edit and merge pull requests without sufficient permissions. The REST API endpoints for PATCH and PUT on pull requests only verify read access, allowing users to close, reopen, retitle, retarget, or merge pull requests on public repositories or as guest collaborators on private repositories without write access.
References
- nvd.nist.gov/vuln/detail/CVE-2026-129863 (opens in a new tab)
- github.com/gitbucket/gitbucket/issues/4179 (opens in a new tab)
- github.com/gitbucket/gitbucket/pull/4181 (opens in a new tab)
- github.com/gitbucket/gitbucket/commit/876c8524967356dfea4a0508c4e1444ad8c80832 (opens in a new tab)
- github.com/gitbucket/gitbucket/blob/4.48.0/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala (opens in a new tab)
- github.com/gitbucket/gitbucket/blob/4.48.0/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala (opens in a new tab)
- hackmd.io/@hieund/gitbucket-pr-api-missing-write-authz (opens in a new tab)
- vulncheck.com/advisories/gitbucket-through-4.48.0-incorrect-authorization-via-pull-request-api-endpoints (opens in a new tab)