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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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.4%, placing it in the 33th 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 September 10, 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 — tpwd/ke_search

GHSA-67j3-jmm3-32xc is a CWE-668 vulnerability in tpwd/ke_search. A fix is available for tpwd/ke_search — see the affected versions and patch details below.

TYPO3 ke_search path traversal from arbitrary table configuration input

Also known asCVE-2026-46723

Published

May 19, 2026

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 1, 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.4%probability of exploitation in next 30 days

Lower Risk+0.09%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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`composer require tpwd/ke_search:^7.0.1`
🐘Packagist	`tpwd/ke_search`	≥ 6.0.0&&< 6.6.1	6.6.1`composer require tpwd/ke_search:^6.6.1`
🐘Packagist	`tpwd/ke_search`	≥ 5.0.0&&< 5.6.2	5.6.2`composer require tpwd/ke_search:^5.6.2`
🐘Packagist	`tpwd/ke_search`	all versions	4.6.7`composer require tpwd/ke_search:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

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?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works