Is tpwd/ke_search 6.6 vulnerable?
Composer · 2 releases from 6.6.0 to 6.6.1 · latest tpwd/ke_search is 7.5.0 · checked 18 Nov 2026
No known advisories in the last release
tpwd/ke_search 6.6.1, the last 6.6 release, has no known advisories. 3 advisories affect earlier 6.6.x releases, so update to 6.6.1.
composer require tpwd/ke_search:^6.6.1Is your project on an affected tpwd/ke_search?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 6.6.x, affecting earlier releases
TYPO3 ke_search path traversal from arbitrary table configuration input
- Affected
- >=7.0.0 <7.0.1 · >=6.0.0 <6.6.1 · >=5.0.0 <5.6.2 · <4.6.7
- Fixed in
- 4.6.7, 5.6.2, 6.6.1, 7.0.1
TYPO3 ke_search path traversal due to lack of normalization on config directory from file indexer
- Affected
- >=7.0.0 <7.0.1 · >=6.0.0 <6.6.1 · >=5.0.0 <5.6.2 · <4.6.7
- Fixed in
- 4.6.7, 5.6.2, 6.6.1, 7.0.1
TYPO3 ke_search XML External Entity Injection
- Affected
- >=7.0.0 <7.0.1 · >=6.0.0 <6.6.1 · >=5.0.0 <5.6.2 · <4.6.7
- Fixed in
- 4.6.7, 5.6.2, 6.6.1, 7.0.1
Every tpwd/ke_search 6.6.x release
Affected: 6.6.0. 6.6.1 is not affected. Latest tpwd/ke_search: 7.5.0.
| Version | Known advisories |
|---|---|
| tpwd/ke_search 6.6.1 | None |
| tpwd/ke_search 6.6.0 | CVE-2026-46723, CVE-2026-46724, CVE-2026-46722 |
Which of your client projects are still on tpwd/ke_search 6.6?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact tpwd/ke_search version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other tpwd/ke_search versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.