Summary
Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19
Insecure temporary directory usage in frontend build functionality of com.vaadin:flow-server versions 2.0.9 through 2.5.2 (Vaadin 14.0.3 through Vaadin 14.5.2), 3.0 prior to 6.0 (Vaadin 15 prior to 19), and 6.0.0 through 6.0.5 (Vaadin 19.0.0 through 19.0.4) allows local users to inject malicious code into frontend resources during application rebuilds.
Impact
GHSA-C57F-4VP2-JQHM has a CVSS score of 6.3 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.5.3, 6.0.6); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
com.vaadin:flow-server to 2.5.3 or later; com.vaadin:flow-server to 6.0.6 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-C57F-4VP2-JQHM? GHSA-C57F-4VP2-JQHM is a medium-severity security vulnerability in com.vaadin:flow-server (maven), affecting versions >= 2.0.9, <= 2.5.2. It is fixed in 2.5.3, 6.0.6.
- How severe is GHSA-C57F-4VP2-JQHM? GHSA-C57F-4VP2-JQHM has a CVSS score of 6.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of com.vaadin:flow-server are affected by GHSA-C57F-4VP2-JQHM? com.vaadin:flow-server (maven) versions >= 2.0.9, <= 2.5.2 is affected.
- Is there a fix for GHSA-C57F-4VP2-JQHM? Yes. GHSA-C57F-4VP2-JQHM is fixed in 2.5.3, 6.0.6. Upgrade to this version or later.
- Is GHSA-C57F-4VP2-JQHM exploitable, and should I be worried? Whether GHSA-C57F-4VP2-JQHM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-C57F-4VP2-JQHM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-C57F-4VP2-JQHM?
- Upgrade
com.vaadin:flow-serverto 2.5.3 or later - Upgrade
com.vaadin:flow-serverto 6.0.6 or later
- Upgrade