DoS (Denial of Service) org.apache.httpcomponents.core5:httpcore5-h2 Dependency in Bitbucket Data Center

XMLWordPrintable

    • 7.5
    • High
    • CVE-2026-54428
    • Atlassian (Internal)
    • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    • DoS (Denial of Service)
    • Bitbucket Data Center

      This High severity DoS (Denial of Service) vulnerability was introduced in version 10.2.0 of Bitbucket Data Center.

      This DoS (Denial of Service) vulnerability, with a CVSS Score of 7.5 and a CVSS Vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H allows an unauthenticated attacker to expose assets in your environment susceptible to exploitation, which has no impact to confidentiality, no impact to integrity, high impact to availability, and requires no user interaction.

      Atlassian recommends that Bitbucket Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions:

      • Bitbucket Data Center 10.2: Upgrade to a release greater than or equal to 10.2.8

      See the release notes (https://confluence.atlassian.com/bitbucketserver/release-notes). You can download the latest
      version of Bitbucket Data Center and Server from the download center
      (https://www.atlassian.com/software/bitbucket/download-archives).

      The National Vulnerability Database provides the following description for this vulnerability:

      Allocation of resources without limits or throttling in the HTTP/2 HPACK decoder in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows an remote attacker to cause a denial of service through memory exhaustion by sending oversized compressed header blocks before the HTTP/2 SETTINGS acknowledgement causes the configured header list size limit to be applied.

              Assignee:
              Unassigned
              Reporter:
              David Detweiler
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: