# CVE-2018-25332: GitBucket 4.23.1 Unauthenticated Remote Code Execution

> Attackers can execute arbitrary system commands by brute-forcing encryption keys and uploading malicious plugins, requiring immediate upgrades.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-5r94-357g-jqj4

## What is CVE-2018-25332?

CVE-2018-25332 is a critical code injection vulnerability in GitBucket, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GitBucket 4.23.1 contains an unauthenticated remote code execution vulnerability that allows attackers to execute arbitrary commands by exploiting weak secret token generation and insecure file upload functionality. Attackers can brute-force the Blowfish encryption key, upload a malicious JAR plugin via the git-lfs endpoint, and execute system commands through an exposed exploit endpoint.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2018-25332?

It affects 1 product.


Products: Gitbucket Gitbucket.

## How do I fix CVE-2018-25332?

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

## Is CVE-2018-25332 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25332 and fix it if it is affected.

What it is: CVE-2018-25332 is a critical code injection vulnerability in GitBucket, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25332 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-2018-25332/ (Markdown: https://insights.sbomify.com/CVE-2018-25332/index.md)
```

## Sources

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

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