How severe is GHSA-67j3-jmm3-32xc?

No CVSS score has been assigned to GHSA-67j3-jmm3-32xc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-67j3-jmm3-32xc?

GHSA-67j3-jmm3-32xc affects the following packages: tpwd/ke_search (Packagist), tpwd/ke_search (Packagist), tpwd/ke_search (Packagist), tpwd/ke_search (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-67j3-jmm3-32xc?

Update tpwd/ke_search to 7.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67j3-jmm3-32xc is resolved across your whole dependency graph.

How do I detect GHSA-67j3-jmm3-32xc in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tpwd/ke_search. 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.

How do I mitigate GHSA-67j3-jmm3-32xc if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-67j3-jmm3-32xc?

O3 pinpoints whether GHSA-67j3-jmm3-32xc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-67j3-jmm3-32xc actively exploited in the wild?

No public exploit code has been indexed for GHSA-67j3-jmm3-32xc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-67j3-jmm3-32xc?

GHSA-67j3-jmm3-32xc has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-67j3-jmm3-32xc?

GHSA-67j3-jmm3-32xc is classified as CWE-668 (CWE-668). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-67j3-jmm3-32xc published, and has it been updated?

GHSA-67j3-jmm3-32xc was published on May 19, 2026 and was last updated on June 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-67j3-jmm3-32xc

GHSA-67j3-jmm3-32xc is a CWE-668 vulnerability in tpwd/ke_search. O3 Security confirms whether GHSA-67j3-jmm3-32xc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

TYPO3 ke_search path traversal from arbitrary table configuration input

Also known asCVE-2026-46723

Published

May 19, 2026

Updated

Jun 29, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Aug 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-67j3-jmm3-32xc.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

4 pkgs affected

🐘tpwd/ke_search🐘tpwd/ke_search🐘tpwd/ke_search🐘tpwd/ke_search

Real-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

In TYPO3 faceted fulltext search (ke_search), theadditional_tables configuration of the page and tt_content indexers accept arbitrary table and field names. A backend user with permission to edit indexer configurations can copy sensitive data from internal TYPO3 tables into the search index. This has been patched in versions 7.0.1, 6.6.1, 5.6.2 and 4.6.7.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`tpwd/ke_search`	≥ 7.0.0&&< 7.0.1	7.0.1
🐘Packagist	`tpwd/ke_search`	≥ 6.0.0&&< 6.6.1	6.6.1
🐘Packagist	`tpwd/ke_search`	≥ 5.0.0&&< 5.6.2	5.6.2
🐘Packagist	`tpwd/ke_search`	all versions	4.6.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tpwd/ke_search. 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 tpwd/ke_search to 7.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67j3-jmm3-32xc 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-67j3-jmm3-32xc 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-67j3-jmm3-32xc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In TYPO3 faceted fulltext search (`ke_search`), the`additional_tables` configuration of the page and `tt_content` indexers accept arbitrary table and field names. A backend user with permission to edit indexer configurations can copy sensitive data from internal TYPO3 tables into the search index. This has been patched in versions 7.0.1, 6.6.1, 5.6.2 and 4.6.7.

O3 Security · Impact-Aware SCA

Is GHSA-67j3-jmm3-32xc in your dependencies?

O3 detects GHSA-67j3-jmm3-32xc across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works