GHSA-vh6j-wv25-8qxr — typo3/flow
GHSA-vh6j-wv25-8qxr is a security vulnerability in typo3/flow. A fix is available for typo3/flow — see the affected versions and patch details below.
Flow Bugfix Releases for Entity Security
Real-World Exposure
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.12composer require typo3/flow:^3.0.12 |
| 🐘Packagist | typo3/flow | ≥ 3.1.0&&< 3.1.10 | 3.1.10composer require typo3/flow:^3.1.10 |
| 🐘Packagist | typo3/flow | ≥ 3.2.0&&< 3.2.13 | 3.2.13composer require typo3/flow:^3.2.13 |
| 🐘Packagist | typo3/flow | ≥ 3.3.0&&< 3.3.13 | 3.3.13composer require typo3/flow:^3.3.13 |
| 🐘Packagist | typo3/flow | ≥ 4.0.0&&< 4.0.6 | 4.0.6composer require typo3/flow:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vh6j-wv25-8qxr can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-vh6j-wv25-8qxr across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.