CVE
GitBucket authorization bypass in pull request API endpoints
Affects GitBucket through 4.48.0 on public repositories, where any authenticated account can reach the pull request API, and on private repositories where a GUEST collaborator can. The REST API is enabled by default.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Public repository, where any authenticated account on the instance can read it. Private repository, where a collaborator holding the read-only GUEST role can reach the endpoints. REST API enabled, which is the default setting.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
GitBucket is affected: any logged-in user can edit or merge pull requests they do not own, using the PATCH and PUT pull request REST API endpoints, which only check read access. An attacker with low privileges can reach this remotely over the network and can close, reopen, retitle, retarget, or merge pull requests into the base branch without write permission.
Original description
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.
Who should check
Anyone running GitBucket through 4.48.0 with multiple user accounts, including public repositories and private repositories with guest collaborators.
“GitBucket through 4.48.0 contains an incorrect authorization vulnerability”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 37 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Public repository, where any authenticated account on the instance can read it. Private repository, where a collaborator holding the read-only GUEST role can reach the endpoints. REST API enabled, which is the default setting.Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129863 (GitBucket through 4.48.0 Incorrect Authorization via Pull Request API Endpoints), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129863 (entry last updated 2026-11-16):
Affected:
- GitBucket GitBucket: through 4.48.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Public repository, where any authenticated account on the instance can read it. (source: https://github.com/gitbucket/gitbucket/issues/4179)
- Private repository, where a collaborator holding the read-only GUEST role can reach the endpoints. (source: https://github.com/gitbucket/gitbucket/issues/4179)
- REST API enabled, which is the default setting. (source: https://github.com/gitbucket/gitbucket/issues/4179)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129863 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129863 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/gitbucket/gitbucket/pull/4181
- https://github.com/gitbucket/gitbucket/commit/876c8524967356dfea4a0508c4e1444ad8c80832
- https://github.com/gitbucket/gitbucket/issues/4179
- https://github.com/gitbucket/gitbucket/blob/4.48.0/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala#L155-L173
- https://github.com/gitbucket/gitbucket/blob/4.48.0/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala#L229-L270
- https://hackmd.io/@hieund/gitbucket-pr-api-missing-write-authz
- https://www.vulncheck.com/advisories/gitbucket-through-4.48.0-incorrect-authorization-via-pull-request-api-endpoints
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129863
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129863"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- GitBucket GitBucket
through 4.48.0
Evidence 9
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 7
- Patch
- Patch
- Report
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129863
Is CVE-2026-129863 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The pull request API endpoints do not enforce write permission. Callers without write access can close, reopen, retitle, retarget, or merge pull requests into the base branch.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-129863?
GitBucket: through 4.48.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions up to and including 4.48.0 are listed as affected. The REST API is enabled by default and accepts a personal access token or the session cookie, so check the GitBucket version in use and whether the REST API is enabled.Source: github.com, vulncheck.com
How do I fix CVE-2026-129863?
The checked facts do not name a fixed version or vendor patch, so no upgrade target can be given here. Check the vendor's advisory for a fix.Source: github.com, vulncheck.com