GHSA-4hhq-j3xw-wj89 is a high-severity (CVSS 8.8) Deserialization of Untrusted Data vulnerability in io.jenkins.plugins:scm-filter-jervis. O3 Security confirms whether GHSA-4hhq-j3xw-wj89 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
RCE vulnerability in SCM Filter Jervis Plugin
Real-World Exposure
io.jenkins.plugins:scm-filter-jervisReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:scm-filter-jervis | all versions | 0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:scm-filter-jervis. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
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.
How O3 protects you
O3 pinpoints whether GHSA-4hhq-j3xw-wj89 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-4hhq-j3xw-wj89. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4hhq-j3xw-wj89 in your dependencies?
O3 detects GHSA-4hhq-j3xw-wj89 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.