Unauthenticated command execution via plugin path traversal
Published May 17, 2026 · Updated May 17, 2026
Remote code execution in GitBucket 4.23.1 allows remote attackers to execute arbitrary Windows commands through the Git LFS endpoint. A four-digit Blowfish key authorizes a crafted Git LFS write whose backslash traversal places an uploaded JAR in the plugins directory. No account is required, but the published chain depends on Windows path handling and the plugin loader executing the planted endpoint.
Summary
What happened
Remote code execution in GitBucket 4.23.1 allows remote attackers to execute arbitrary Windows commands through the Git LFS endpoint. A four-digit Blowfish key authorizes a crafted Git LFS write whose backslash traversal places an uploaded JAR in the plugins directory. No account is required, but the published chain depends on Windows path handling and the plugin loader executing the planted endpoint.
The record
- CVE
- CVE-2018-25332
- Published
- May 17, 2026
- Updated
- May 17, 2026
- Vendor
- GitBucket
- Product
- GitBucket
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2026CVE publishedPublication date reported by the CVE source.
- May 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.23.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitBucket 4.23.1 Remote Code Executionproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo