{"answers":{"affected":"2 open source packages ship an affected version, including maatwebsite/excel.","exploited":"There is no known exploitation of CVE-2026-84374 in the wild and no public exploit code.","fix":"Upgrade maatwebsite/excel to 3.1.70 or later.","what":"CVE-2026-84374 is a high-severity path traversal vulnerability in SpartnerNL Laravel-Excel, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-84374 and fix it if it is affected.\n\nWhat it is: CVE-2026-84374 is a high-severity path traversal vulnerability in SpartnerNL Laravel-Excel, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-84374 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- maatwebsite/excel (Packagist): affected from 3.1.8; fixed in 3.1.70\n- maatwebsite/excel (Packagist): affected from 3.1.8; fixed in 3.1.70\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-84374/ (Markdown: https://insights.sbomify.com/CVE-2026-84374/index.md)","id":"CVE-2026-84374","markdown":"https://insights.sbomify.com/CVE-2026-84374/index.md","name":"CVE-2026-84374","record":{"aliases":["GHSA-c7r6-vx3h-w5g2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel Excel library","requires_auth":"low_privilege","summary":"Attackers can overwrite arbitrary files via path traversal in Laravel Excel exports, potentially achieving remote code execution if PHP files are targeted.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Laravel Excel provides supercharged Excel exports and imports in Laravel. From 3.1.8 until 3.1.70, in src/Files/Disk.php the Maatwebsite\\Excel\\Files\\Disk::copy() method resolves the caller-controlled $destination supplied through Excel::store(), $export-\u003estore(), or storeExcel() against the process working directory with realpath() instead of the configured filesystem disk. If the path names an existing writable file, Disk::copy() opens it with fopen() in rb+ mode and uses stream_copy_to_stream(), bypassing Flysystem path confinement and allowing an attacker whose application input controls the export path to overwrite arbitrary existing files with export content. The rb+ behavior creates a non-truncating overwrite and trailing bytes when the new export is shorter, and overwriting an executable PHP file can lead to remote code execution. This issue is fixed in version 3.1.70.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Laravel Excel writes exports outside the configured filesystem disk when given a caller-controlled path","id":"CVE-2026-84374","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources","id":"CVE-2026-84375"},"packages":[{"ecosystem":"Packagist","fixed":["3.1.70"],"introduced":["3.1.8"],"last_affected":[],"package":"maatwebsite/excel","purl":null,"source":"GHSA-c7r6-vx3h-w5g2"},{"ecosystem":"Packagist","fixed":["3.1.70"],"introduced":["3.1.8"],"last_affected":[],"package":"maatwebsite/excel","purl":"pkg:composer/maatwebsite/excel","source":"GHSA-c7r6-vx3h-w5g2"}],"prev":{"headline":"Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock","id":"CVE-2026-84373"},"products":["Laravel-Excel"],"published":"2026-09-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-04","vendors":["SpartnerNL"]},"summary":"Attackers can overwrite arbitrary files via path traversal in Laravel Excel exports, potentially achieving remote code execution if PHP files are targeted.","url":"https://insights.sbomify.com/CVE-2026-84374/"}