How severe is CVE-2019-10390?

CVE-2019-10390 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-2019-10390 being actively exploited?

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

What products are affected by CVE-2019-10390?

CVE-2019-10390 affects Jenkins Splunk. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-10390?

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-2019-10390 published?

CVE-2019-10390 was published on 2019-08-28 and last updated on 2026-06-17.

CVE-2019-10390

CVE-2019-10390 is a high-severity vulnerability in Jenkins Splunk 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.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.5
EPSS exploit prediction: 2% (74th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jenkins Splunk
Published: 2019-08-28
Last modified: 2026-06-17

Description

A sandbox bypass vulnerability in Jenkins Splunk Plugin 1.7.4 and earlier allowed attackers with Overall/Read permission to provide a Groovy script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM.

Frequently asked questions

What is CVE-2019-10390?: A sandbox bypass vulnerability in Jenkins Splunk Plugin 1.7.4 and earlier allowed attackers with Overall/Read permission to provide a Groovy script to an HTTP endpoint that can result in arbitrary code execution on the Jenkins master JVM.
How severe is CVE-2019-10390?: CVE-2019-10390 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-2019-10390 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (74th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-10390?: CVE-2019-10390 affects Jenkins Splunk. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-10390?: 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-2019-10390 published?: CVE-2019-10390 was published on 2019-08-28 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:jenkins:splunk:*:*:*:*:*:jenkins:*:*