# CVE-2026-13540: GitBucket RepositoryCreationService.scala Git.cloneRepository.setURI server-side request forgery

> Remote attackers can exploit a server-side request forgery flaw in GitBucket's repository creation service to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-29f2-r2fr-hjv6

## What is CVE-2026-13540?

CVE-2026-13540 is a medium-severity server-side request forgery vulnerability in GitBucket, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in GitBucket up to 4.46.1. This affects the function Git.cloneRepository.setURI of the file src/main/scala/gitbucket/core/service/RepositoryCreationService.scala. Performing a manipulation of the argument url results in server-side request forgery. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. The patch is named 487a9b980f56aa73b6a044b1e86a92eed5043215. To fix this issue, it is recommended to deploy a patch.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-13540?


## How do I fix CVE-2026-13540?

No fix has been published for CVE-2026-13540 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13540 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13540 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13540 and fix it if it is affected.

What it is: CVE-2026-13540 is a medium-severity server-side request forgery vulnerability in GitBucket, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13540 exists.

Affected product: GitBucket. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13540/ (Markdown: https://insights.sbomify.com/CVE-2026-13540/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13540
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13540
- OSV: https://osv.dev/vulnerability/CVE-2026-13540

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13540/
Summaries are generated and may contain mistakes; the official description above is the record.