CVE-2019-11831
No exploitation reported by the sources we read.
- Published2019-05-09
- Fixed in8.7.1 · 8.6.16 · 7.67 · 7.67.0
- WeaknessCWE-22 · CWE-502
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
The PharStreamWrapper (aka phar-stream-wrapper) package 2.x before 2.1.1 and 3.x before 3.1.1 for TYPO3 does not prevent directory traversal, which allows attackers to bypass a deserialization protection mechanism, as demonstrated by a phar:///path/bad.phar/../good.phar URL.
Timeline
dates in UTC- 2019-05-0904:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-11831?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-11831?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.7 | ≥ 8.7.0, < 8.7.1 | 8.7.1 | NVD · OSV |
| 8.6 | ≥ 8.6.0, < 8.6.16 | 8.6.16 | NVD |
| 8.x | ≥ 8.0.0, < 8.6.16 | 8.6.16 | OSV |
| 7.x | ≥ 7.0, < 7.67 | 7.67 | NVD |
| 7.x | ≥ 7.0.0, < 7.67.0 | 7.67.0 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 28.x | = 28 | no fix published | NVD |
| 29.x | = 29 | no fix published | NVD |
| 30.x | = 30 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | = 8.0 | no fix published | NVD |
| 9.0 | = 9.0 | no fix published | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Drupal to 8.7.1 · 8.6.16 · 7.67 · 7.67.0
Advisories and patches
- github.comRelease Notes
- github.comRelease Notes
- typo3.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-22, CWE-502read 2026-10-23
- FIRST EPSSEPSS score5.4 %2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2019-05-09
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-11831?
Is CVE-2019-11831 actively exploited?
What is the CVSS score for CVE-2019-11831?
Running typo3/phar-stream-wrapper? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.