GitHub Enterprise - The best way to build and ship software

The 2.17 series release notes contain important changes in this release series.

Security Fixes

MEDIUM: An attacker could push a malicious GitHub Pages branch with overlapping submodule names, possibly leading to remote code execution within the GitHub Pages build container. To exploit this vulnerability, an attacker would need permission to create a branch within a repository on the GitHub Enterprise Server instance. CVE-2019-1387
Packages have been updated to the latest security versions.

Unknown locales were generating errors when running commands in the administrative shell.
ghe-config-check was returning validation errors for github-ssl.acme.ca-conf and syslog.cert.
The Let's Encrypt certificate registration feature consistently failed following an update to the external API.
Upgrades could fail due to a missing SQL table.
Commit objects could be lost in some cases if an update of a replica failed and then a repair operation was ran.
A GraphQL query to retrieve the additions and deletions for a changed binary file returned a 500 error.
Audit log did not include some entries when changing protected branches settings.

On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user.
Custom firewall rules aren't maintained during an upgrade.
Subversion (SVN) checkout may timeout while the repository data cache is being built. In most cases, subsequent svn checkout attempts will succeed.
Git LFS tracked files uploaded through the web interface are incorrectly added directly to the repository.
Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters.
Lines in gists are not selectable.
When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.

Thanks!

The GitHub Team