Unsafe Deserialization in tomasnorre/crawler (CVE-2026-8727)
Summary
Vulnerability in tomasnorre/crawler (CVE-2026-8727). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 11.0.13 or later.
Original description
The description as published by the source.
The Crawler extension passes the X-T3Crawler-Meta response header from crawled URLs directly to PHP's unserialize(). An attacker controlling a crawled endpoint can inject arbitrary serialized PHP objects, leading to Remote Code Execution on the TYPO3 server. Exploitation requires administrative privileges to configure a crawler-enabled page and trigger the crawl via a Scheduler task.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-8727 has been found in tomasnorre/crawler.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tomasnorre/crawler to 11.0.13 or later.
If unsure, ask your IT team or search "tomasnorre/crawler CVE-2026-8727" on the vendor's site.
CVE-2026-8727 (tomasnorre/crawler) — CWE-502
Patched: 11.0.13 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in tomasnorre/crawler.
Check the vendor advisory for the affected versions of tomasnorre/crawler.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 11.0.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tomasnorre/crawler' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tomasnorre/crawler' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tomasnorre/crawlerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tomasnorre/crawler to 11.0.13ステージング環境で 11.0.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory typo3.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web packagist.org