How severe is CVE-2019-10418?

CVE-2019-10418 has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-10418?

CVE-2019-10418 affects the following packages: io.fabric8.pipeline:kubernetes-pipeline-arquillian-steps (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10418?

The records we use list no patched version of io.fabric8.pipeline:kubernetes-pipeline-arquillian-steps for CVE-2019-10418. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.fabric8.pipeline:kubernetes-pipeline-arquillian-steps, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

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

CVE-2019-10418 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th 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-10418 published, and has it been updated?

CVE-2019-10418 was published on September 25, 2019 and was last updated on October 24, 2026. 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

CRITICAL severity

CVE-2019-10418 — kubernetes-pipeline-arqui…

CRITICAL

CVE-2019-10418 is a critical-severity (CVSS 9.9) vulnerability in io.fabric8.pipeline:kubernetes-pipeline-arquillian-steps. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Incorrect Authorization in Jenkins Kubernetes :: Pipeline :: Arquillian Steps Plugin

Also known asGHSA-f46p-q6jh-226m

Published

Sep 25, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

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

☕io.fabric8.pipeline:kubernetes-pipeline-arquillian-steps

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 Kubernetes :: Pipeline :: Arquillian Steps Plugin provides a custom whitelist for script security that allowed attackers to invoke arbitrary methods, bypassing typical sandbox protection.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.fabric8.pipeline:kubernetes-pipeline-arquillian-steps`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

kubernetes pipelinejenkins

≤ 1.6

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.fabric8.pipeline:kubernetes-pipeline-arquillian-steps, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of io.fabric8.pipeline:kubernetes-pipeline-arquillian-steps for CVE-2019-10418. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

Jenkins Kubernetes :: Pipeline :: Arquillian Steps Plugin provides a custom whitelist for script security that allowed attackers to invoke arbitrary methods, bypassing typical sandbox protection.

O3 Security · Impact-Aware SCA

Is CVE-2019-10418 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works