How severe is CVE-2025-27515?

No CVSS score has been assigned to CVE-2025-27515 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-27515?

CVE-2025-27515 affects the following packages: laravel/framework (Packagist), laravel/framework (Packagist), laravel/framework (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-27515?

Update laravel/framework to 12.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27515 is resolved across your whole dependency graph.

How do I detect CVE-2025-27515 in my Packagist dependencies?

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

How do I mitigate CVE-2025-27515 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 CVE-2025-27515 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-27515 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 CVE-2025-27515?

CVE-2025-27515 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, 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 CVE-2025-27515?

CVE-2025-27515 is classified as CWE-155 (CWE-155). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-27515 published, and has it been updated?

CVE-2025-27515 was published on March 5, 2025 and was last updated on October 28, 2026. 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

CVE-2025-27515 — framework

Fix: laravel/framework@2d13303

CVE-2025-27515 is a CWE-155 vulnerability in laravel/framework. A fix is available for laravel/framework — see the affected versions and patch details below.

Laravel has a File Validation Bypass

Also known asBIT-laravel-2025-27515GHSA-78fx-h6xr-vch4

Published

Mar 5, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%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

3 pkgs affected

🐘laravel/framework🐘laravel/framework🐘laravel/framework

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

Laravel is a web application framework. When using wildcard validation to validate a given file or image field (files.*), a user-crafted malicious request could potentially bypass the validation rules. This vulnerability is fixed in 11.44.1 and 12.1.1.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`laravel/framework`	≥ 12.0.0&&< 12.1.1	12.1.1`composer require laravel/framework:^12.1.1`
🐘Packagist	`laravel/framework`	≥ 11.0.0&&< 11.44.1	11.44.1`composer require laravel/framework:^11.44.1`
🐘Packagist	`laravel/framework`	all versions	10.48.29`composer require laravel/framework:^10.48.29`

Affected Products

1 product · 2 configurations

Application

frameworklaravel

≥ 12.0.0 && < 12.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for laravel/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update laravel/framework to 12.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27515 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

Laravel is a web application framework. When using wildcard validation to validate a given file or image field (`files.*`), a user-crafted malicious request could potentially bypass the validation rules. This vulnerability is fixed in 11.44.1 and 12.1.1.

O3 Security · Impact-Aware SCA

Is CVE-2025-27515 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works