How severe is CVE-2025-54068?

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

Which packages are affected by CVE-2025-54068?

CVE-2025-54068 affects the following packages: livewire/livewire (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-54068?

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

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for livewire/livewire. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-54068 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.

How does O3 Security protect against CVE-2025-54068?

O3 pinpoints whether CVE-2025-54068 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-54068 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2025-54068, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-54068?

CVE-2025-54068 has an EPSS (Exploit Prediction Scoring System) score of 95.4%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-54068 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-54068 (Laravel Livewire Code Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-03-20. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-04-03. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-54068?

CVE-2025-54068 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2025-54068?

A Nuclei detection template exists for CVE-2025-54068, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

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

CVE-2025-54068 was published on July 17, 2025 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-03-20 — agencies required to remediate by 2026-04-03

🐘 Packagist

CVE-2025-54068

Livewire vulnerable to remote command execution during property update hydration

Also known asGHSA-29cq-5w36-x7w3

Published

Jul 17, 2025

Updated

Jul 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

95.4%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘livewire/livewire

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

Livewire is a full-stack framework for Laravel. In Livewire v3 up to and including v3.6.3, a vulnerability allows unauthenticated attackers to achieve remote command execution in specific scenarios. The issue stems from how certain component property updates are hydrated. This vulnerability is unique to Livewire v3 and does not affect prior major versions. Exploitation requires a component to be mounted and configured in a particular way, but does not require authentication or user interaction. This issue has been patched in Livewire v3.6.4. All users are strongly encouraged to upgrade to this version or later as soon as possible. No known workarounds are available.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`livewire/livewire`	≥ 3.0.0-beta.1&&< 3.6.4	3.6.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

synacktiv/Livepyre

A tool designed to exploit CVE-2025-54068 and Remote Command Execution i

⭐ 148🍴 35Jul 2026

HelgeSverre/livewire-honeypot

High-interaction honeypot mimicking a vulnerable Laravel/Livewire app. C

⭐ 6🍴 0May 2026

haxorstars/CVE-2025-54068

A tool designed to exploit CVE-2025-54068 and Remote Command Execution o

⭐ 5🍴 1May 2026

z0d131482700x/Livewire2025CVE

Fast Python scanner detects vulnerable Laravel Livewire v3 sites (CVE-20

⭐ 3🍴 0Jan 2026

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for livewire/livewire. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update livewire/livewire to 3.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-54068 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.
How O3 protects you
O3 pinpoints whether CVE-2025-54068 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-54068. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-54068 in your dependencies?

O3 detects CVE-2025-54068 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works