Is typo3/phar-stream-wrapper vulnerable?

Composer typo3/phar-stream-wrapper has 4 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

4advisories
2critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2019-11831Directory Traversal in typo3/phar-stream-wrappercritical9.8>=2.0.0 and <2.1.1 or >=3.0.0 and <3.1.12.1.1, 3.1.1
CVE-2019-11830PharStreamWrapper for Typo3 unsafe deserialization vulnerabilitycritical9.8>=2.0.0 and <2.1.1 or >=3.0.0 and <3.1.12.1.1, 3.1.1
2018-10-18-1By-passing Protection of PharStreamWrapper Interceptorunknown0.0>=1.0.0 and <2.0.0 or >=2.0.0 and <2.0.1 or >=3.0.0 and <3.0.12.0.1, 3.0.1
GHSA-4v5g-8pq2-32m2By-passing Protection of PharStreamWrapper Interceptormedium0.0>=1.0.0 and <2.0.1 or >=3.0.0 and <3.0.12.0.1, 3.0.1

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.