CVE-2019-15000
No exploitation reported by the sources we read.
- Published2019-09-19
- Fixed in6.5.2 · 6.4.3 · 6.3.5 · 6.2.6 · 6.1.8 · 6.0.10
- WeaknessCWE-78
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The commit diff rest endpoint in Bitbucket Server and Data Center before 5.16.10 (the fixed version for 5.16.x ), from 6.0.0 before 6.0.10 (the fixed version for 6.0.x), from 6.1.0 before 6.1.8 (the fixed version for 6.1.x), from 6.2.0 before 6.2.6 (the fixed version for 6.2.x), from 6.3.0 before 6.3.5 (the fixed version for 6.3.x), from 6.4.0 before 6.4.3 (the fixed version for 6.4.x), and from 6.5.0 before 6.5.2 (the fixed version for 6.5.x) allows remote attackers who have permission to access a repository, if public access is enabled for a project or repository then attackers are able to exploit this issue anonymously, to read the contents of arbitrary files on the system and execute commands via injecting additional arguments into git commands.
Timeline
dates in UTC- 2019-09-1915:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-15000?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-15000?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.5 | ≥ 6.5.0, < 6.5.2 | 6.5.2 | NVD |
| 6.4 | ≥ 6.4.0, < 6.4.3 | 6.4.3 | NVD |
| 6.3 | ≥ 6.3.0, < 6.3.5 | 6.3.5 | NVD |
| 6.2 | ≥ 6.2.0, < 6.2.6 | 6.2.6 | NVD |
| 6.1 | ≥ 6.1.0, < 6.1.8 | 6.1.8 | NVD |
| 6.0 | ≥ 6.0.0, < 6.0.10 | 6.0.10 | NVD |
| 5.16 | ≥ 5.16.0, < 5.16.10 | 5.16.10 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Atlassian bitbucket to 6.5.2 · 6.4.3 · 6.3.5 · 6.2.6 · 6.1.8 · 6.0.10 · 5.16.10
Advisories and patches
- jira.atlassian.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- NVDweakness (CWE)CWE-78read 2026-10-23
- FIRST EPSSEPSS score7.8 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2019-09-19
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-15000?
Is CVE-2019-15000 actively exploited?
What is the CVSS score for CVE-2019-15000?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.