How severe is CVE-2017-8448?

CVE-2017-8448 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-8448 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-8448?

CVE-2017-8448 primarily affects Elastic X-pack. In total, 15 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-8448?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-8448 published?

CVE-2017-8448 was published on 2017-09-29 and last updated on 2026-06-17.

CVE-2017-8448

CVE-2017-8448 is a high-severity vulnerability in Elastic X-pack with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-269.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.5
EPSS exploit prediction: 1% (54th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-269
Affected product: Elastic X-pack
Published: 2017-09-29
Last modified: 2026-06-17

Description

An error was found in the permission model used by X-Pack Alerting 5.0.0 to 5.6.0 whereby users mapped to certain built-in roles could create a watch that results in that user gaining elevated privileges.

Frequently asked questions

What is CVE-2017-8448?: An error was found in the permission model used by X-Pack Alerting 5.0.0 to 5.6.0 whereby users mapped to certain built-in roles could create a watch that results in that user gaining elevated privileges.
How severe is CVE-2017-8448?: CVE-2017-8448 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-8448 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-8448?: CVE-2017-8448 primarily affects Elastic X-pack. In total, 15 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-8448?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-8448 published?: CVE-2017-8448 was published on 2017-09-29 and last updated on 2026-06-17.

References

https://discuss.elastic.co/t/x-pack-alerting-and-kibana-5-6-1-security-update/101884

Affected products (15)

cpe:2.3:a:elastic:x-pack:5.0.0:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.0.1:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.0.2:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.1.1:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.2.0:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.2.1:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.2.2:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.3.0:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.3.1:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.3.2:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.3.3:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.4.0:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.5.0:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.5.2:*:*:*:*:*:*:*
cpe:2.3:a:elastic:x-pack:5.6.0:*:*:*:*:*:*:*

More vulnerabilities in Elastic X-pack

CVE-2018-3822 — Critical (CVSS 9.8): X-Pack Security versions 6.2.0, 6.2.1, and 6.2.2 are vulnerable to a user impersonation attack via incorrect XML…
CVE-2017-8438 — High (CVSS 8.8): Elastic X-Pack Security versions 5.0.0 to 5.4.0 contain a privilege escalation bug in the run_as functionality. This…
CVE-2017-8450 — High (CVSS 7.5): X-Pack 5.1.1 did not properly apply document and field level security to multi-search and multi-get requests so users…
CVE-2017-8447 — Medium (CVSS 6.5): An error was found in the X-Pack Security 5.3.0 to 5.5.2 privilege enforcement. If a user has either 'delete' or…
CVE-2017-8442 — Medium (CVSS 6.5): Elasticsearch X-Pack Security versions 5.0.0 to 5.4.3, when enabled, can result in the Elasticsearch _nodes API leaking…
CVE-2017-8449 — Medium (CVSS 5.9): X-Pack Security 5.2.x would allow access to more fields than the user should have seen if the field level security…

All CVEs affecting Elastic X-pack →

Other CWE-269 (Improper Privilege Management) vulnerabilities

CVE-2026-31852 — Critical (CVSS 10.0): Jellyfin is an open-source media system. The code-quality.yml GitHub Actions workflow in jellyfin/jellyfin-ios is…
CVE-2025-20282 — Critical (CVSS 10.0): A vulnerability in an internal API of Cisco ISE and Cisco ISE-PIC could allow an unauthenticated, remote attacker to…
CVE-2025-0505 — Critical (CVSS 10.0): On Arista CloudVision systems (virtual or physical on-premise deployments), Zero Touch Provisioning can be used to gain…
CVE-2023-48418 — Critical (CVSS 10.0): In checkDebuggingDisallowed of DeviceVersionFragment.java, there is a possible way to access adb before SUW…
CVE-2023-48419 — Critical (CVSS 10.0): An attacker in the wifi vicinity of a target Google Home can spy on the victim, resulting in Elevation of Privilege
CVE-2023-31273 — Critical (CVSS 10.0): Protection mechanism failure in some Intel DCM software before version 5.2 may allow an unauthenticated user to…

Browse all CWE-269 (Improper Privilege Management) vulnerabilities →