The 2.12 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.
- 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.
- Git LFS, release and issue assets, user profile images, webhooks, or Subversion access may be unavailable if an appliance is restarted after applying the 2.12.5 or greater hotpatch—if this occurs, please contact Enterprise Support for assistance.
The GitHub Team