By-passing Protection of PharStreamWrapper Interceptor

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Insecure deserialization is a vulnerability which occurs when untrusted data is used to abuse the logic of an application. In July 2018, the vulnerability of insecure deserialization when executing Phar archives was addressed by removing the known attack vector in the TYPO3 core. For more details read the corresponding TYPO3 advisory. In addition, a new interceptor was introduced to protect possible (but unknown) vulnerabilities in 3rd party components like TYPO3 extensions. Basically, the PharStreamWrapper intercepts direct invocations of Phar archives and allows or denies further processing based on individual rules. Recently, the PharStreamWrapper was extracted from the TYPO3 core and released as standalone package under the MIT license. It is now available for any PHP driven project. The stream wrapper overwrites the existing Phar handling of PHP, applies its own assertions and then restores the native PHP Phar handling for the corresponding commands (e.g. fileexists, include,…

Published by the source

5 Jun 2024, 17:30 UTC

Last modified by the source

5 Jun 2024, 17:30 UTC

Source last checked

26 Oct 2026, 14:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4v5g-8pq2-32m2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-4v5g-8pq2-32m2

Advisory: By-passing Protection of PharStreamWrapper Interceptor
IDs: GHSA-4v5g-8pq2-32m2
Record: https://patchnext.com/advisories/ghsa-4v5g-8pq2-32m2 (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/phar-stream-wrapper 3.0.1, 2.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/phar-stream-wrapper: affected >= 1.0.0, < 2.0.1; >= 3.0.0, < 3.0.1; fixed in 2.0.1, 3.0.1

## Suggested inspection (read-only)
- Packagist typo3/phar-stream-wrapper: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/phar-stream-wrapper.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4v5g-8pq2-32m2 (GitHub-reviewed advisory GHSA-4v5g-8pq2-32m2 lists affected ranges: Packagist typo3/phar-stream-wrapper >=1.0.0 =3.0.0 <3.0.1)

Commands are suggestions: review each one before running it.