Carbon has an arbitrary file include via unvalidated input passed to Carbon::setLocale

Exploitation

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

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-22145: 0.75% estimated exploitation activity in the next 30 days; percentile 55.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Application passing unsanitized user input to Carbon::setLocale are at risk of arbitrary file include, if the application allows users to upload files with .php extension in an folder that allows include or require to read it, then they are at risk of arbitrary code ran on their servers. Patches - 3.8.4 - 2.72.6 Workarounds Any of the below actions can be taken to prevent the issue: - Validate input before calling setLocale(), for instance by forbidding or removing / and \ - Call setLocale() only with a locale from a whitelist of supported locales - When uploading files, rename them so they cannot have a .php extension (this is recommended even if you're not affected by this issue) - Prefer storage system that are not local to the application (remote service, or local service ran by another user so the uploaded files actually live outside of the application basedir) References https://en.wikipedia.org/wiki/Fileinclusionvulnerability Credits Thanks to Szczepan Hołyszewski who…

Published by the source

8 Jan 2025, 21:03 UTC

Last modified by the source

25 Feb 2025, 18:39 UTC

Source last checked

26 Oct 2026, 14:29 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j3f9-p6hm-5w6q

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

# Patch Next advisory brief: CVE-2025-22145

Advisory: Carbon has an arbitrary file include via unvalidated input passed to Carbon::setLocale
IDs: CVE-2025-22145, GHSA-j3f9-p6hm-5w6q
Record: https://patchnext.com/advisories/cve-2025-22145 (revision 1, source checked 26 Oct 2026, 14:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nesbot/carbon 3.8.4, 2.72.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist nesbot/carbon: affected >= 3.0.0, < 3.8.4; < 2.72.6; fixed in 2.72.6, 3.8.4

## Suggested inspection (read-only)
- Packagist nesbot/carbon: 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 nesbot/carbon.
- 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-j3f9-p6hm-5w6q (GitHub-reviewed advisory GHSA-j3f9-p6hm-5w6q lists affected ranges: Packagist nesbot/carbon >=3.0.0 =0 <2.72.6)

Commands are suggestions: review each one before running it.