Laravel Excel writes exports outside the configured filesystem disk when given a caller-controlled path
CVE-2026-84374GHSA-c7r6-vx3h-w5g2
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (maatwebsite/excel 3.1.70), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist maatwebsite/excel
- Affected
- >= 3.1.8, < 3.1.70
- Fixed in
- 3.1.70
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-c7r6-vx3h-w5g2 lists affected ranges: Packagist maatwebsite/excel >=3.1.8 <3.1.70 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-c7r6-vx3h-w5g2 lists affected ranges: Packagist maatwebsite/excel >=3.1.8 <3.1.70
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-84374: 0.84% estimated exploitation activity in the next 30 days; percentile 57.96 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Excel::store() resolved the destination path against the process working directory rather than the configured filesystem disk. When that path resolved to an existing file, the export was written straight to it with fopen(), bypassing the disk entirely. An application that passes a user-controlled value as the export path could therefore be made to overwrite an arbitrary existing file that the PHP process can write to, with content the user controls. Details Maatwebsite\Excel\Files\Disk::copy() contained two paths: $destination is the $filePath argument given to Excel::store(), $export-store() or -storeExcel(). realpath() resolves it against the current working directory — public/ for a typical web request — not against the disk root. On a hit, the write went directly to the filesystem and never reached Flysystem, which would otherwise have rejected ../ traversal and confined absolute paths to the disk root. The disk argument was effectively ignored for those paths, including…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-c7r6-vx3h-w5g2
- Revision 1 · created ·
Published from osv record GHSA-c7r6-vx3h-w5g2
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-84374 Advisory: Laravel Excel writes exports outside the configured filesystem disk when given a caller-controlled path IDs: CVE-2026-84374, GHSA-c7r6-vx3h-w5g2 Record: https://patchnext.com/advisories/cve-2026-84374 (revision 2, source checked 26 Oct 2026, 14:53 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: maatwebsite/excel 3.1.70. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist maatwebsite/excel: affected >= 3.1.8, < 3.1.70; fixed in 3.1.70 ## Suggested inspection (read-only) - Packagist maatwebsite/excel: 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 maatwebsite/excel. - 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://osv.dev/vulnerability/GHSA-c7r6-vx3h-w5g2 (OSV record GHSA-c7r6-vx3h-w5g2 lists affected ranges: Packagist maatwebsite/excel >=3.1.8 <3.1.70 (fixed)) - Verified: https://github.com/advisories/GHSA-c7r6-vx3h-w5g2 (GitHub-reviewed advisory GHSA-c7r6-vx3h-w5g2 lists affected ranges: Packagist maatwebsite/excel >=3.1.8 <3.1.70) Commands are suggestions: review each one before running it.
Loading voting…