How severe is GHSA-j3f9-p6hm-5w6q?

No CVSS score has been assigned to GHSA-j3f9-p6hm-5w6q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j3f9-p6hm-5w6q?

GHSA-j3f9-p6hm-5w6q affects the following packages: nesbot/carbon (Packagist), nesbot/carbon (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-j3f9-p6hm-5w6q?

Update nesbot/carbon to 3.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3f9-p6hm-5w6q is resolved across your whole dependency graph.

How do I detect GHSA-j3f9-p6hm-5w6q in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nesbot/carbon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j3f9-p6hm-5w6q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-j3f9-p6hm-5w6q actively exploited in the wild?

No public exploit code has been indexed for GHSA-j3f9-p6hm-5w6q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j3f9-p6hm-5w6q?

GHSA-j3f9-p6hm-5w6q has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j3f9-p6hm-5w6q?

GHSA-j3f9-p6hm-5w6q is classified as CWE-98 (CWE-98). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j3f9-p6hm-5w6q published, and has it been updated?

GHSA-j3f9-p6hm-5w6q was published on January 8, 2025 and was last updated on February 25, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Carbon has an arbitrary file include via unvalidated input passed to Carbon::setLocaleGHSA-j3f9-p6hm-5w6q

Fix: briannesbitt/Carbon@129700e

GHSA-j3f9-p6hm-5w6q is a CWE-98 vulnerability in nesbot/carbon. A fix is available for nesbot/carbon — see the affected versions and patch details below.

Also known asCVE-2025-22145

Published

Jan 8, 2025

Updated

Feb 25, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j3f9-p6hm-5w6q.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐘nesbot/carbon🐘nesbot/carbon

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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/File_inclusion_vulnerability

Credits

Thanks to Szczepan Hołyszewski who reported the issue and to Tidelift to coordinate the resolution

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`nesbot/carbon`	≥ 3.0.0&&< 3.8.4	3.8.4`composer require nesbot/carbon:^3.8.4`
🐘Packagist	`nesbot/carbon`	all versions	2.72.6`composer require nesbot/carbon:^2.72.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nesbot/carbon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nesbot/carbon to 3.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3f9-p6hm-5w6q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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](https://github.com/briannesbitt/Carbon/releases/tag/3.8.4) - [2.72.6](https://github.com/briannesbitt/Carbon/releases/tag/2.72.6) ### Workarounds Any of the below actions can be taken to prevent the issue: - Validate input before calling `setLocale()`, for instance by

O3 Security · Impact-Aware SCA

Is GHSA-j3f9-p6hm-5w6q in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works