Bitbucket 7.21 (LTS)
Bitbucket 7.21 (LTS)
The Bitbucket 7.21 (LTS) reached end of service life on Feb 28, 2024 — Bitbucket no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Bitbucket 7.21 (LTS) incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- bitbucket
- release
- 7.21
- product Label
- Bitbucket
- release Label
- 7.21 (LTS)
- codename
- lts
- true
- latest Version
- 7.21.23
- release Date
- 2022-02-28
- maintained
- source Url
- https://endoflife.date/bitbucket
Lifecycle Dates
- End of Service Life
- Feb 28, 2024
- Last OEM Support
- Feb 28, 2024
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Bitbucket 7.21 (LTS) — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Bitbucket 7.21 (LTS)?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Bitbucket 7.21 (LTS) when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Bitbucket 7.21 (LTS) Support: Frequently Asked Questions
Is the Bitbucket 7.21 (LTS) still supported?
Bitbucket ended support for the Bitbucket 7.21 (LTS) on Feb 28, 2024 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Bitbucket 7.21 (LTS) end of service life (EOSL) date?
Bitbucket lists the end of service life for the Bitbucket 7.21 (LTS) as Feb 28, 2024.
Can I keep using the Bitbucket 7.21 (LTS) after its EOSL date?
Yes. EOSL means Bitbucket stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Bitbucket 7.21 (LTS) cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Bitbucket 7.21 (LTS)
4 published CVEs affect the Bitbucket 7.21 (LTS), including 4 rated critical or high severity. Bitbucket no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2022-43781 | CRITICAL | 9.8 | Nov 17, 2022 | There is a command injection vulnerability using environment variables in Bitbucket Server and Data Center. An attacker with permission to control their username can exploit this issue to execute arbitrary code on the system. This vulnerability can be unauthenticated if the Bitbucket Server and Data Center instance has enabled “Allow public signup”. |
| CVE-2022-26136 | CRITICAL | 9.8 | Jul 20, 2022 | A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to bypass Servlet Filters used by first and third party apps. The impact depends on which filters are used by each app, and how the filters are used. This vulnerability can result in authentication bypass and cross-site scripting. Atlassian has released updates that fix the root cause of this vulnerability, but has not exhaustively enumerated all potential consequences of this vulnerability. Atlassian Bamboo |
| CVE-2022-36804 | HIGH | 8.8 | Aug 25, 2022 | Multiple API endpoints in Atlassian Bitbucket Server and Data Center 7.0.0 before version 7.6.17, from version 7.7.0 before version 7.17.10, from version 7.18.0 before version 7.21.4, from version 8.0.0 before version 8.0.3, from version 8.1.0 before version 8.1.3, and from version 8.2.0 before version 8.2.2, and from version 8.3.0 before 8.3.1 allows remote attackers with read permissions to a public or private Bitbucket repository to execute arbitrary code by sending a malicious HTTP request. |
| CVE-2022-26137 | HIGH | 8.8 | Jul 20, 2022 | A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to cause additional Servlet Filters to be invoked when the application processes requests or responses. Atlassian has confirmed and fixed the only known security issue associated with this vulnerability: Cross-origin resource sharing (CORS) bypass. Sending a specially crafted HTTP request can invoke the Servlet Filter used to respond to CORS requests, resulting in a CORS bypass. An attacker that can trick a |