Expression Language Injection in Netflix ConductorGHSA-wfj5-2mqr-7jvv
CRITICALGHSA-wfj5-2mqr-7jvv is a critical-severity (CVSS 9.8) Expression Language Injection vulnerability in com.netflix.conductor:conductor-core. A fix is available for com.netflix.conductor:conductor-core — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-wfj5-2mqr-7jvv by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
com.netflix.conductor:conductor-coreReal-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
Netflix Conductor uses Java Bean Validation (JSR 380) custom constraint validators. When building custom constraint violation error messages, different types of interpolation are supported, including Java EL expressions. If an attacker can inject arbitrary data in the error message template being passed to ConstraintValidatorContext.buildConstraintViolationWithTemplate() argument, they will be able to run arbitrary Java code.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.netflix.conductor:conductor-core | all versions | 2.25.4com.netflix.conductor:conductor-core:2.25.4 |
Affected Products
conductornetflixDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.netflix.conductor:conductor-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.netflix.conductor:conductor-core to 2.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wfj5-2mqr-7jvv is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-wfj5-2mqr-7jvv in your dependencies?
Find it across Maven, including transitive dependencies.