Summary
Neos Flow Information disclosure in entity security
If you had used entity security and wanted to secure entities not just based on the user's role, but on some property of the user (like the company he belongs to), entity security did not work properly together with the doctrine query cache. This could lead to other users re-using SQL queries from the cache which were built for other users; and thus users could see entities which were not destined for them.
Am I affected?
- Do you use Entity Security? if no, you are not affected.
- You disabled the Doctrine Cache (Flow_Persistence_Doctrine)? If this is the case, you are not affected.
- You use Entity Security in custom Flow or Neos applications. Read on.
- If you only used Entity Security based on roles (i.e. role A was allowed to see entities, but role B was denied): In this case, you are not affected.
- If you did more advanced stuff using Entity Security (like checking that a customer only sees his own orders; or a hotel only sees its own bookings), you very likely needed to register a custom global object in Neos.Flow.aop.globalObjects. In this case, you are affected by the issue; and need to implement the CacheAwareInterface in your global object for proper caching.
All Flow versions (starting in version 3.0, where Entity Security was introduced) were affected.
Impact
GHSA-9CW3-J7WG-JWJ8 has a CVSS score of 4.3 (Medium). The vector is network-reachable, 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 (3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.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
neos/flow to 3.0.12 or later; neos/flow to 3.1.10 or later; neos/flow to 3.2.13 or later; neos/flow to 3.3.13 or later; neos/flow to 4.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-9CW3-J7WG-JWJ8? GHSA-9CW3-J7WG-JWJ8 is a medium-severity security vulnerability in neos/flow (composer), affecting versions >= 3.0.0, < 3.0.12. It is fixed in 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6.
- How severe is GHSA-9CW3-J7WG-JWJ8? GHSA-9CW3-J7WG-JWJ8 has a CVSS score of 4.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 neos/flow are affected by GHSA-9CW3-J7WG-JWJ8? neos/flow (composer) versions >= 3.0.0, < 3.0.12 is affected.
- Is there a fix for GHSA-9CW3-J7WG-JWJ8? Yes. GHSA-9CW3-J7WG-JWJ8 is fixed in 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6. Upgrade to this version or later.
- Is GHSA-9CW3-J7WG-JWJ8 exploitable, and should I be worried? Whether GHSA-9CW3-J7WG-JWJ8 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-9CW3-J7WG-JWJ8 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-9CW3-J7WG-JWJ8?
- Upgrade
neos/flowto 3.0.12 or later - Upgrade
neos/flowto 3.1.10 or later - Upgrade
neos/flowto 3.2.13 or later - Upgrade
neos/flowto 3.3.13 or later - Upgrade
neos/flowto 4.0.6 or later
- Upgrade