GHSA-vh6j-wv25-8qxr
Flow Bugfix Releases for Entity Security
Blast Radius
typo3/flow🐘typo3/flow🐘typo3/flow🐘typo3/flow🐘typo3/flowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/flow | ≥ 3.0.0&&< 3.0.12 | 3.0.12 |
| 🐘Packagist | typo3/flow | ≥ 3.1.0&&< 3.1.10 | 3.1.10 |
| 🐘Packagist | typo3/flow | ≥ 3.2.0&&< 3.2.13 | 3.2.13 |
| 🐘Packagist | typo3/flow | ≥ 3.3.0&&< 3.3.13 | 3.3.13 |
| 🐘Packagist | typo3/flow | ≥ 4.0.0&&< 4.0.6 | 4.0.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/flow. 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 typo3/flow to 3.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vh6j-wv25-8qxr 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-vh6j-wv25-8qxr 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-vh6j-wv25-8qxr. 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-vh6j-wv25-8qxr in your dependencies?
O3 detects GHSA-vh6j-wv25-8qxr across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.