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

Security Fixes

• HIGH: Improper sanitization of user markup content, while not allowing full XSS, could have been abused to leak sensitive data or perform actions as the user viewing the content.
• LOW: A file path traversal vulnerability in the Management Console API could allow authenticated users to download content of local files ending with .txt.
• LOW: Improper sanitization of input allowed splitting of a response header value over multiple lines. No headers could be injected because the actual header name was included on each line.
• LOW: Detect and reject any Git content that shows evidence of being part of a SHA-1 collision attack
• Packages have been updated to the latest security versions.

Bug Fixes

• The webhook delivery log was missing timing metrics.
• The /trending page could incorrectly display a Sign up for free button.
• ghe-check-disk-usage incorrectly defaulted to a --verbose run.
• When migrating from GitHub.com or another GitHub Enterprise appliance, an @ could cause comments to be truncated.
• Status checks on a pull request weren't properly run after using the Update branch button, so the Merge pull request button was inaccessible.
• Processes responsible for Git repository replication could cause a high availability replica appliance to run out of memory and kill a dependent service.
• After an upgrade, the Management Console of a high availability replica appliance could indefinitely show the Starting... page.
• The total number of organizations was incorrect because the count included trusted OAuth applications.
• Exceptions were logged to /var/log/github/exceptions.log when a reaction was added a comment.
• It wasn't possible to give LDAP mapped access to a repository when transferring a repository to an organization.
• Administrators couldn't restore deleted LFS objects.
• When a SAML user whose normalized username matches an organization's name tried to authenticate, the organization's attributes such as profile email could be incorrecty altered.
• The org_repos count in /enterprise/stats incorrectly counted private user-owned forks.
• It was possible to queue more jobs to repair a search index through the site admin than could be processed in a reasonable time, causing low priority jobs to become backlogged.
• A configuration run could revert an SSL certificate to an automatically generated self-signed certificate.
• Graphs in the Management Console monitoring page were incorrectly sorted.

Changes

• Site admin reports are now accessible with a site_admin scoped OAuth token.
• GitHub Flavored Markdown, which is now compliant with CommonMark, is used to render repository markdown (e.g. .md) files. (updated 2017-06-11)

Upcoming deprecation of GitHub Enterprise 2.6

GitHub Enterprise 2.6 will be deprecated as of April 26, 2017. That means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, upgrade to the newest version of GitHub Enterprise as soon as possible.

Known Issues

• We incorrectly redirect to the dashboard if you accessed GitHub Enterprise using an alias while in private mode. This might happen if you set a fully qualified domain name but the subdomain resolves correctly.
• Images uploaded to issues save with an absolute URL, so they can be broken if the hostname changes.
• On a freshly set up GitHub Enterprise without any users, an attacker could create the first admin user.
• Custom firewall rules aren't maintained during an upgrade.
• Enqueued background jobs are sometimes not purged when a repository is deleted.
• 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.
• GitHub Enterprise clustering can not be configured without https.
• The /status endpoint on a high availability replica incorrectly returns 200 OK instead of 503 Service Unavailable.
• Site administrators can experience a 500 Internal Server Error after viewing the history for a file path containing Japanese characters. (updated 2017-03-30)
• Deleting a search index doesn't delete all associated metadata, which are then incorrectly reused if a new search index is created. This causes search index repair jobs to be reported as finished in the site admin when they were not. (updated 2017-03-30)
• During maintenance mode for a high availability environment, the /setup/maintenance does not list active processes. (updated 2017-03-30)
• An issue or pull request comment containing the string "User-Agent: GitHub-Hookshot" incorrectly triggers a firewall rule and causes an internal server error on several pages, including the author's profile page. (updated 2017-03-30)
• collectd metric paths can be truncated, which causes multiple write attempts to the same file for different metrics. (updated 2017-07-10)
• After changing the visibility of a repository, wiki search results have a conflicting number of displayed search results. Administrators can reindex the wiki through the site admin dashboard. (updated 2017-11-09)
• The create team API endpoint returns a 500 error if LDAP Sync is enabled and the team already exists. (updated 2018-01-09)

Thanks!

The GitHub Team