How severe is CVE-2019-10390?

CVE-2019-10390 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-10390?

CVE-2019-10390 affects the following packages: com.splunk.splunkins:splunk-devops (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10390?

Update com.splunk.splunkins:splunk-devops to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10390 is resolved across your whole dependency graph.

How do I detect CVE-2019-10390 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.splunk.splunkins:splunk-devops, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-10390 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-2019-10390 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-10390 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-2019-10390?

CVE-2019-10390 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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.

When was CVE-2019-10390 published, and has it been updated?

CVE-2019-10390 was published on May 24, 2022 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2019-10390 — splunk-devops

HIGHFix: jenkinsci/splunk-devops-plugin@58db287

CVE-2019-10390 is a high-severity (CVSS 8.8) remote code execution vulnerability in com.splunk.splunkins:splunk-devops. A fix is available for com.splunk.splunkins:splunk-devops — see the affected versions and patch details below.

Jenkins Splunk Plugin Sandbox Bypass

Published

May 24, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% 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

☕com.splunk.splunkins:splunk-devops

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

Description

Jenkins Splunk Plugin has a form validation HTTP endpoint used to validate a user-submitted Groovy script through compilation, which was not subject to sandbox protection. This allowed attackers with Overall/Read access to execute arbitrary code on the Jenkins controller by applying AST transforming annotations such as @Grab to source code elements.

The affected HTTP endpoint now applies a safe Groovy compiler configuration preventing the use of unsafe AST transforming annotations.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.splunk.splunkins:splunk-devops`	all versions	1.8.0`com.splunk.splunkins:splunk-devops:1.8.0`

Affected Products

1 product · 1 configurations

Application

splunkjenkins

≤ 1.7.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.splunk.splunkins:splunk-devops, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.splunk.splunkins:splunk-devops to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10390 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-10390 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works