CVE-2026-129863

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-16. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-126457 (ENISA EUVD) · GHSA-jv75-83vr-pf2w (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan mitigationThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2026

Last Modified

November 16, 2026

Advisory Details (7)

Auto-updated Nov 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
Web page

GitBucket through 4.48.0 Incorrect Authorization via Pull Request API Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitbucket-through-4.48.0-incorrect-authorization-via-pull-request-api-endpoints
Web page

GitBucket REST API lets a read-only user merge and modify pull requests they cannot write to - HackMD

https://hackmd.io/@hieund/gitbucket-pr-api-missing-write-authz
Web page

gitbucket/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala at 4.48.0 · gitbucket/gitbucket · GitHub

https://github.com/gitbucket/gitbucket/blob/4.48.0/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala#L229-L270
Web page

gitbucket/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala at 4.48.0 · gitbucket/gitbucket · GitHub

https://github.com/gitbucket/gitbucket/blob/4.48.0/src/main/scala/gitbucket/core/controller/api/ApiPullRequestControllerBase.scala#L155-L173
GitHub commit

commit 876c85249673 (gitbucket/gitbucket)

Fix landed in gitbucket/gitbucket commit 876c85249673 — awaiting tagged release

https://github.com/gitbucket/gitbucket/commit/876c8524967356dfea4a0508c4e1444ad8c80832
GitHub pull request

Fix Pull Request permission check in REST API

Fix merged in gitbucket/gitbucket PR #4181 on 2026-11-14 — awaiting tagged release

https://github.com/gitbucket/gitbucket/pull/4181
Web page

Security: REST API can merge/edit pull requests with only read access (referrersOnly instead of writableUsersOnly) · Issue #4179 · gitbucket/gitbucket · GitHub

https://github.com/gitbucket/gitbucket/issues/4179

Vendor Advisories for CVE-2026-129863(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-11-20 05:43 UTCEchelonGraph re-scored
  4. 2026-11-20 05:43 UTCGHSA enrichmentGHSA-jv75-83vr-pf2w · GitHub severity HIGH · GitHub CVSS 6.5
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-11-16 17:47 UTCEchelonGraph re-scored
  9. 2026-11-16 17:47 UTCGHSA enrichmentGHSA-jv75-83vr-pf2w · GitHub severity HIGH · GitHub CVSS 6.5
  10. 2026-11-16 17:29 UTCEchelonGraph re-scored
  11. 2026-11-16 17:29 UTCGHSA enrichmentGHSA-jv75-83vr-pf2w · GitHub severity HIGH · GitHub CVSS 6.5
  12. 2026-11-16 16:55 UTCEchelonGraph re-scored
  13. 2026-11-16 16:55 UTCGHSA enrichmentGHSA-jv75-83vr-pf2w · GitHub severity HIGH · GitHub CVSS 6.5
  14. 2026-11-16 16:02 UTCENISA EUVD ID recordedEUVD-2026-126457 · Source: ENISA EUVD
  15. 2026-11-16 15:29 UTCEchelonGraph re-scored
  16. 2026-11-16 14:40 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  17. 2026-11-16 14:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129863?
CVE-2026-129863 is a medium-severity vulnerability; its CVE record was published on November 16, 2026. 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…
When was CVE-2026-129863 made public?
CVE-2026-129863 was made public on November 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 16, 2026. EchelonGraph's copy of the record carries a last-modified date of November 16, 2026; the record at its source may have been updated since.
Is CVE-2026-129863 actively exploited?
CVE-2026-129863 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129863?
CVE-2026-129863 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129863?
An upstream fix for CVE-2026-129863 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-129863 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-129863

Explore →

Is Your Infrastructure Affected by CVE-2026-129863?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.