What is CVE-2022-29567?

CVE-2022-29567 is a medium-severity security vulnerability in com.vaadin:vaadin (maven), affecting versions >= 14.8.5, < 14.8.10. It is fixed in 14.8.10, 22.0.15, 23.0.9.

How severe is CVE-2022-29567?

CVE-2022-29567 has a CVSS score of 5.7 (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 packages are affected by CVE-2022-29567?

com.vaadin:vaadin (maven) versions >= 14.8.5, = 14.8.5, < 14.8.10.

Is there a fix for CVE-2022-29567?

Yes. CVE-2022-29567 is fixed in 14.8.10, 22.0.15, 23.0.9. Upgrade to this version or later.

Is CVE-2022-29567 exploitable, and should I be worried?

Whether CVE-2022-29567 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.

What actually determines whether CVE-2022-29567 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.

CVE-2022-29567 in com.vaadin:vaadin

Q: How severe is CVE-2022-29567?

CVE-2022-29567 has a CVSS score of 5.7 (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.

Q: Which packages are affected by CVE-2022-29567?

com.vaadin:vaadin (maven) versions >= 14.8.5, = 14.8.5, < 14.8.10.

Q: Is there a fix for CVE-2022-29567?

Yes. CVE-2022-29567 is fixed in 14.8.10, 22.0.15, 23.0.9. Upgrade to this version or later.

Q: Is CVE-2022-29567 exploitable, and should I be worried?

Whether CVE-2022-29567 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.

Q: What actually determines whether CVE-2022-29567 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.

Q: How do I fix CVE-2022-29567?

Upgrade: com.vaadin:vaadin to 14.8.10 or later, com.vaadin:vaadin to 22.0.15 or later, com.vaadin:vaadin to 23.0.9 or later, com.vaadin:vaadin-grid-flow to 14.8.10 or later, com.vaadin:vaadin-grid-flow to 22.0.15 or later, com.vaadin:vaadin-grid-flow to 23.0.9 or later.

Summary

Possible information disclosure inside TreeGrid component with default data provider

Description

The default configuration of a TreeGrid component uses Object::toString as a key on the client-side and server communication in Vaadin 14.8.5 through 14.8.9, 22.0.6 through 22.0.14, 23.0.0.beta2 through 23.0.8 and 23.1.0.alpha1 through 23.1.0.alpha4, resulting in potential information disclosure of values that should not be available on the client-side.

Impact

CVE-2022-29567 has a CVSS score of 5.7 (Medium). The vector is network-reachable, low privileges required, and user interaction required. 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 (14.8.10, 22.0.15, 23.0.9); upgrading removes the vulnerable code path.

Affected versions

com.vaadin:vaadin (>= 14.8.5, < 14.8.10) com.vaadin:vaadin (>= 22.0.6, < 22.0.15) com.vaadin:vaadin (>= 23.0.0, < 23.0.9) com.vaadin:vaadin-grid-flow (>= 14.8.5, < 14.8.10) com.vaadin:vaadin-grid-flow (>= 22.0.6, < 22.0.15) com.vaadin:vaadin-grid-flow (>= 23.0.0.beta2, < 23.0.9)

Security releases

com.vaadin:vaadin → 14.8.10 (maven) com.vaadin:vaadin → 22.0.15 (maven) com.vaadin:vaadin → 23.0.9 (maven) com.vaadin:vaadin-grid-flow → 14.8.10 (maven) com.vaadin:vaadin-grid-flow → 22.0.15 (maven) com.vaadin:vaadin-grid-flow → 23.0.9 (maven)

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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

com.vaadin:vaadin to 14.8.10 or later; com.vaadin:vaadin to 22.0.15 or later; com.vaadin:vaadin to 23.0.9 or later; com.vaadin:vaadin-grid-flow to 14.8.10 or later; com.vaadin:vaadin-grid-flow to 22.0.15 or later; com.vaadin:vaadin-grid-flow to 23.0.9 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-29567? CVE-2022-29567 is a medium-severity security vulnerability in com.vaadin:vaadin (maven), affecting versions >= 14.8.5, < 14.8.10. It is fixed in 14.8.10, 22.0.15, 23.0.9.
How severe is CVE-2022-29567? CVE-2022-29567 has a CVSS score of 5.7 (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 packages are affected by CVE-2022-29567?
- com.vaadin:vaadin (maven) (versions >= 14.8.5, < 14.8.10)
- com.vaadin:vaadin-grid-flow (maven) (versions >= 14.8.5, < 14.8.10)
Is there a fix for CVE-2022-29567? Yes. CVE-2022-29567 is fixed in 14.8.10, 22.0.15, 23.0.9. Upgrade to this version or later.
Is CVE-2022-29567 exploitable, and should I be worried? Whether CVE-2022-29567 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 CVE-2022-29567 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 CVE-2022-29567?
- Upgrade com.vaadin:vaadin to 14.8.10 or later
- Upgrade com.vaadin:vaadin to 22.0.15 or later
- Upgrade com.vaadin:vaadin to 23.0.9 or later
- Upgrade com.vaadin:vaadin-grid-flow to 14.8.10 or later
- Upgrade com.vaadin:vaadin-grid-flow to 22.0.15 or later
- Upgrade com.vaadin:vaadin-grid-flow to 23.0.9 or later

Other vulnerabilities in com.vaadin:vaadin

CVE-IDSeverityPackage summary

CVE-2026-2742Mediumcom.vaadin:flow-server: Vaadin Vulnerable to Authentication Bypass When Accessing the /VAADIN Endpoint Without a Trailing Slash CVE-2025-15022Mediumcom.vaadin:vaadin-server: Vaadin vulnerable to Cross-site Scripting GHSA-C7V7-RQFM-F44JMediumcom.vaadin:vaadin: Vaadin Platform possible file bypass via upload validation on the server-side CVE-2023-25499Mediumcom.vaadin:vaadin: Vaadin vulnerable to possible information disclosure in non visible components.CVE-2023-25500Lowcom.vaadin:flow-server: Vaadin vulnerable to possible information disclosure of class and method names in RPC response