NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

RCE vulnerability in SCM Filter Jervis PluginGHSA-4hhq-j3xw-wj89

HIGHFix: jenkinsci/scm-filter-jervis-plugin@a36e8bd

GHSA-4hhq-j3xw-wj89 is a high-severity (CVSS 8.8) Deserialization of Untrusted Data vulnerability in io.jenkins.plugins:scm-filter-jervis. A fix is available for io.jenkins.plugins:scm-filter-jervis — see the affected versions and patch details below.

Also known asCVE-2020-2189
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk
0.31%1.13%1.96%2.78%0.8%2.3%May 26Sep 26Nov 26

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.jenkins.plugins:scm-filter-jervis

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

SCM Filter Jervis Plugin 0.2.1 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types. This results in a remote code execution (RCE) vulnerability exploitable by users able to configure jobs with the filter, or control the contents of a previously configured job’s SCM repository.

SCM Filter Jervis Plugin 0.3 configures its YAML parser to only instantiate safe types.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.jenkins.plugins:scm-filter-jervisall versions0.3io.jenkins.plugins:scm-filter-jervis:0.3

Affected Products

1 product · 1 configurations
Application
source code management filter jervisjenkins
≤ 0.2.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:scm-filter-jervis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.jenkins.plugins:scm-filter-jervis to 0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4hhq-j3xw-wj89 is resolved across your whole dependency graph.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

SCM Filter Jervis Plugin 0.2.1 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types. This results in a remote code execution (RCE) vulnerability exploitable by users able to configure jobs with the filter, or control the contents of a previously configured job’s SCM repository. SCM Filter Jervis Plugin 0.3 configures its YAML parser to only instantiate safe types.
O3 Security · Impact-Aware SCA

Is GHSA-4hhq-j3xw-wj89 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
RCE vulnerability in SCM Filter Jervis Plugin (High 8.8)