CVE-2017-7500 [High] | Security Vulnerability in Rpm

It was found that rpm did not properly handle RPM installations when a destination path was a symbolic link to a directory, possibly changing ownership and permissions of an arbitrary directory, and RPM files being placed in an arbitrary destination. An attacker, with write access to a directory in which a subdirectory will be installed, could redirect that directory to an arbitrary location and gain root privilege.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.05%	0.41%	+0.36%
2	2026-06-06	0.05%	0.05%	+0.01%
3	2026-05-25	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.05%

0.41%

+0.36%

2026-06-06

0.05%

+0.01%

2026-05-25

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.3	3.0	HIGH	`CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. 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.3	5.9	[email protected]
7.8	3.0	HIGH	`CVSS:3.0/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.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.3

3.0

HIGH

CVSS:3.0/AV:L/AC:L/PR:L/UI:R/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:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.3

5.9

[email protected]

7.8

3.0

HIGH

CVSS:3.0/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.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-2017-7500

vendor	priority	summary	link
`debian`	unimportant	CVE-2017-7500 unimportant priority: Debian including 1 source packages (rpm), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5.	https://security-tracker.debian.org/tracker/CVE-2017-7500
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2017-7500
`suse`	high	CVE-2017-7500 severity important: SUSE including 344 source package names (0.1.0:rpm-4.14.1-10.3.1, 0.1.75:rpm-4.14.1-10.3.1, …), 585 product×package rows across 157 product lines (Container caasp/v4/389-ds, Container caasp/v4/busybox, … (157 product lines)): Fixed 270, Known Affected 231, Known Not Affected 84.	https://www.suse.com/security/cve/CVE-2017-7500/
`ubuntu`	low	CVE-2017-7500 low priority: Ubuntu including 1 source packages (rpm), 22 status rows across 22 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 13, ignored 6, needed 3.	https://ubuntu.com/security/CVE-2017-7500

Affected software / configurations for CVE-2017-7500

Vendor	Product	Version	Raw CPE
rpm	rpm	>= 4.13.0.0, < 4.13.0.2	cpe:2.3:a:rpm:rpm::::::::
rpm	rpm	4.14.0.0	cpe:2.3:a:rpm:rpm:4.14.0.0:rc1::::::
rpm	rpm	4.14.0.0	cpe:2.3:a:rpm:rpm:4.14.0.0:rc2::::::

References for CVE-2017-7500

URL	Tags
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7500	Issue Tracking
https://github.com/rpm-software-management/rpm/commit/c815822c8bdb138066ff58c624ae83e3a12ebfa9	Third Party Advisory
https://github.com/rpm-software-management/rpm/commit/f2d3be2a8741234faaa96f5fd05fdfdc75779a79	Third Party Advisory

URL

CVE-2017-7500

Exploit prediction scoring system (EPSS) score for CVE-2017-7500

Common vulnerability scoring system (CVSS) metrics for CVE-2017-7500

Weakness enumeration for CVE-2017-7500

OS Trackers for CVE-2017-7500

Affected software / configurations for CVE-2017-7500

References for CVE-2017-7500