How severe is CVE-2017-15111?

CVE-2017-15111 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-15111?

CVE-2017-15111 affects the following packages: keycloak-httpd-client-install (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2017-15111?

Update keycloak-httpd-client-install to 0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-15111 is resolved across your whole dependency graph.

How do I detect CVE-2017-15111 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keycloak-httpd-client-install, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-15111 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-15111 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-15111 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-15111?

CVE-2017-15111 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-15111?

CVE-2017-15111 is classified as CWE-377 (CWE-377), CWE-59 (CWE-59). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-15111 published, and has it been updated?

CVE-2017-15111 was published on January 20, 2018 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2017-15111 — keycloak-httpd-client-ins…

MEDIUMFix: jdennis/keycloak-httpd-client-install@07f26e2

CVE-2017-15111 is a medium-severity (CVSS 5.5) CWE-377 vulnerability in keycloak-httpd-client-install. A fix is available for keycloak-httpd-client-install — see the affected versions and patch details below.

keycloak-httpd-client-install symlink attack vulnerability

Also known asGHSA-vqf9-v3hc-wr54PYSEC-2026-829

Published

Jan 20, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍keycloak-httpd-client-install

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

keycloak-httpd-client-install versions before 0.8 insecurely creates temporary file allowing local attackers to overwrite other files via symbolic link.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keycloak-httpd-client-install`	all versions	0.8`pip install --upgrade 'keycloak-httpd-client-install==0.8'`

Affected Products

1 product · 1 configurations

Application

keycloak-httpd-client-installkeycloak-httpd-client-install_project

< 0.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keycloak-httpd-client-install, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keycloak-httpd-client-install to 0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-15111 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Red Hat Product Security has rated this issue as having security impact of Low. This issue may be fixed in a future version of Red Hat Enterprise Linux. OpenStack users please note, this issue is present in: * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack…

Product	Fixed in	Advisory
Red Hat Enterprise Linux 7	`keycloak-httpd-client-install-0:0.8-1.el7`	RHSA-2019:2137

Frequently Asked Questions

keycloak-httpd-client-install versions before 0.8 insecurely creates temporary file allowing local attackers to overwrite other files via symbolic link.

O3 Security · Impact-Aware SCA

Is CVE-2017-15111 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.5/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-377CWE-377 CWE-59CWE-59

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jan 20, 2018

Last updated

Oct 20, 2026

Identifiers

CVE-2017-15111

GHSA-vqf9-v3hc-wr54

PYSEC-2026-829

References

Advisoryaccess.redhat.com · RHSA 2019:2137 Advisorynvd.nist.gov · CVE 2017 15111 Fixgithub.com · 07f26e213196936fb328ea0c1d5a66a09d8b5440 Packagegithub.com · keycloak httpd client install

Related vulnerabilities

Also affects keycloak-httpd-client-install

This CVE is medium severity; 1 of 1 other CVE affecting keycloak-httpd-client-install is rated as high or higher (top: high).

CVE-2017-15112

Same weakness: CWE-377

This CVE is medium severity; 5 of 7 other CVEs with CWE-377 are rated as high or higher (top: high).

CVE-2026-113713CVE-2026-64672CVE-2026-62847CVE-2026-106451CVE-2026-55086CVE-2026-35342CVE-2026-53759Browse all CWE-377

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2017-15111 — keycloak-httpd-client-ins…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2017-15111 in your dependencies?