CVE-2019-18276 [High] | Security Vulnerability in Bash

An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

EDB-ID	Source	Kind	Published	Link
—	nvd_ref	exploit_tag		Exploit-DB ↗
—	nvd_ref	exploit_tag		Exploit-DB ↗

EDB-ID

Source

Kind

Published

Link

—

nvd_ref

exploit_tag

Exploit-DB ↗

—

nvd_ref

exploit_tag

Exploit-DB ↗

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	50.22%	2.61%	-47.62%
2	2026-05-02	49.61%	50.22%	+0.61%
3	2025-11-24	—	49.61%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

50.22%

2.61%

-47.62%

2026-05-02

49.61%

50.22%

+0.61%

2025-11-24

—

49.61%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. 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.	1.8	5.9	[email protected]
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. 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.	1.8	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0
7.2	2.0	HIGH	`AV:L/AC:L/Au:N/C:C/I:C/A:C` Click to expand Access vector (AV:L) Requires local access to the target system. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:C) Complete confidentiality impact. Integrity impact (I:C) Complete integrity impact. Availability impact (A:C) Complete availability impact.	3.9	10.0	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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.

1.8

5.9

[email protected]

7.8

3.1

HIGH

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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.

1.8

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

7.2

2.0

HIGH

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

Access vector (AV:L): Requires local access to the target system.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:C): Complete confidentiality impact.
Integrity impact (I:C): Complete integrity impact.
Availability impact (A:C): Complete availability impact.

3.9

10.0

[email protected]

OS Trackers for CVE-2019-18276

vendor	priority	summary	link
`alpine`	—	CVE-2019-18276: 1 source package rows (bash); 5 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 5.	https://security.alpinelinux.org/vuln/CVE-2019-18276
`debian`	unimportant	CVE-2019-18276 unimportant priority: Debian including 1 source packages (bash), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2019-18276
`gentoo`	normal	CVE-2019-18276: 1 GLSA(s) (202105-34), 1 atom(s) (app-shells/bash); latest impact normal.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-18276
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2019-18276
`suse`	low	CVE-2019-18276 severity low: SUSE including 12 source package names (bash, bash-4.4.19-14.el8, …), 54 product×package rows across 15 product lines (SUSE Liberty Linux 8, SUSE Linux Enterprise High Performance Computing 12 SP5, … (15 product lines)): Will Not Fix 52, Fixed 2.	https://www.suse.com/security/cve/CVE-2019-18276/
`ubuntu`	low	CVE-2019-18276 low priority: Ubuntu including 1 source packages (bash), 11 status rows across 11 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, trusty, upstream, xenial): released 5, ignored 3, not-affected 3.	https://ubuntu.com/security/CVE-2019-18276

Affected software / configurations for CVE-2019-18276

Vendor	Product	Version	Raw CPE
gnu	bash	<= 5.0	cpe:2.3:a:gnu:bash::::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:beta1::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:beta2::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch1::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch10::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch11::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch2::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch3::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch4::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch5::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch6::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch7::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch8::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:patch9::::::
gnu	bash	5.0	cpe:2.3:a:gnu:bash:5.0:rc1::::::
netapp	hci_management_node	—	cpe:2.3:a:netapp:hci_management_node:-:::::::*
netapp	oncommand_unified_manager	>= 9.5	cpe:2.3:a:netapp:oncommand_unified_manager::::::vmware_vsphere::*
netapp	solidfire	—	cpe:2.3:a:netapp:solidfire:-:::::::*
oracle	communications_cloud_native_core_policy	1.14.0	cpe:2.3:a:oracle:communications_cloud_native_core_policy:1.14.0:::::::*

References for CVE-2019-18276

URL	Tags
http://packetstormsecurity.com/files/155498/Bash-5.0-Patch-11-Privilege-Escalation.html	Exploit Third Party Advisory VDB Entry
https://github.com/bminor/bash/commit/951bdaad7a18cc0dc1036bba86b18b90874d39ff	Patch Third Party Advisory
https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
https://security.gentoo.org/glsa/202105-34	Third Party Advisory
https://security.netapp.com/advisory/ntap-20200430-0003/	Third Party Advisory
https://www.oracle.com/security-alerts/cpuapr2022.html	Patch Third Party Advisory
https://www.youtube.com/watch?v=-wGtxJ8opa8	Exploit Third Party Advisory

URL

CVE-2019-18276

Public exploit references (Exploit-DB) for CVE-2019-18276

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

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

Weakness enumeration for CVE-2019-18276

OS Trackers for CVE-2019-18276

Affected software / configurations for CVE-2019-18276

References for CVE-2019-18276