The 2.11 series release notes contain important changes in this release series.
- LOW: A malicious user could execute a 'tab-nabbing' attack by exploiting
window.opener when linking from GitHub Enterprise hosted Markdown content.
- Packages have been updated to the latest security versions.
- Promoting a replica could take an excessive amount of time in a multi-replica environment.
- Self-signed TLS certificates would fail to generate on Azure instances.
- Tags created through a release contained incomplete reflog data
- Organizations could be incorrectly suspended via the Suspend User REST API.
- Email visibility could be incorrectly toggled via the REST API.
- Fixes an issue where rate limits on raw and archive endpoints were left enabled even when configured to be disabled.
- Users can no longer accidentally upload revoked PGP keys.
- Users can no longer accidentally upload their private PGP keys.
- Optimise Elasticsearch backup process by preferring local copies of indices.
Upcoming deprecation of GitHub Enterprise 2.11
GitHub Enterprise 2.11 will be deprecated as of September 13, 2018. 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.
- 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.
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.
- Pull request review comments migrated with
ghe-migrator are displayed in the wrong order.
- The pull request review request has users reversed, after migration with
- The comment count in the "Conversation" tab of a pull request migrated with
ghe-migrator can be wrong.
gpgverify service may consume large amounts of CPU time even when not processing requests.
The GitHub Team