CVE-2019-20097 [High] | RCE in Bitbucket

Bitbucket Server and Bitbucket Data Center versions starting from 1.0.0 before 5.16.11, from version 6.0.0 before 6.0.11, from version 6.1.0 before 6.1.9, from version 6.2.0 before 6.2.7, from version 6.3.0 before 6.3.6, from version 6.4.0 before 6.4.4, from version 6.5.0 before 6.5.3, from version 6.6.0 before 6.6.3, from version 6.7.0 before 6.7.3, from version 6.8.0 before 6.8.2, from version 6.9.0 before 6.9.1 had a Remote Code Execution vulnerability via the post-receive hook. A remote attacker with permission to clone and push files to a repository on the victim's Bitbucket Server or Bitbucket Data Center instance, can exploit this vulnerability to execute arbitrary commands on the Bitbucket Server or Bitbucket Data Center systems, using a file with specially crafted content.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	2.85%	2.48%	-0.37%
2	2026-04-21	2.99%	2.85%	-0.15%
3	2025-12-28	—	2.99%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

2.85%

2.48%

-0.37%

2026-04-21

2.99%

2.85%

-0.15%

2025-12-28

—

2.99%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]
6.5	2.0	MEDIUM	`AV:N/AC:L/Au:S/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	8.0	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

6.5

2.0

MEDIUM

AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

8.0

6.4

[email protected]

Affected software / configurations for CVE-2019-20097

Vendor	Product	Version	Raw CPE
atlassian	bitbucket	>= 1.0.0, < 5.6.11	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.0.0, < 6.0.11	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.1.0, < 6.1.9	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.2.0, < 6.2.7	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.3.0, < 6.3.6	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.4.0, < 6.4.4	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.5.0, < 6.5.3	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.6.0, < 6.6.3	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.7.0, < 6.7.3	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.8.0, < 6.8.2	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.9.0, < 6.9.1	cpe:2.3:a:atlassian:bitbucket::::::::

References for CVE-2019-20097

URL	Tags
https://jira.atlassian.com/browse/BSERV-12099	Issue Tracking Patch Vendor Advisory

URL

CVE-2019-20097

Exploit prediction scoring system (EPSS) score for CVE-2019-20097

Common vulnerability scoring system (CVSS) metrics for CVE-2019-20097

Weakness enumeration for CVE-2019-20097

Affected software / configurations for CVE-2019-20097

References for CVE-2019-20097