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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-54068 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

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 96.3%, 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 October 21, 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

CISA KEV · ACTIVELY EXPLOITED

CVE-2025-54068 — livewire

Fix: livewire/livewire@ef04be7

CVE-2025-54068 is a Code Injection vulnerability in livewire/livewire. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-03-20) — treat it as actively exploited and patch now. A fix is available for livewire/livewire — see the affected versions and patch details below.

Livewire vulnerable to remote command execution during property update hydration

Also known asGHSA-29cq-5w36-x7w3

Published

Jul 17, 2025

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-03-20. Federal agencies were required to remediate by 2026-04-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-54068.

EPSS Exploitation Probability

via FIRST.org ↗

96.3%probability of exploitation in next 30 days

Very High Risk-0.79%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

Real-World Exposure

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

Impact

In Livewire v3 (≤ 3.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.

Patches

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.

Workarounds

There is no known workaround at this time. Users are strongly advised to upgrade to a patched version immediately.

Resources

No public references available at this time to avoid exposure. Details will be published after a responsible disclosure window.

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`composer require livewire/livewire:^3.6.4`

Affected Products

1 product · 1 configurations

Application

livewirelaravel

≥ 3.0.0 && < 3.6.4

range

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

⭐ 150🍴 34Sep 2026

HelgeSverre/livewire-honeypot

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

⭐ 6🍴 0Aug 2026

haxorstars/CVE-2025-54068

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

⭐ 5🍴 1Jul 2026

e4zyy/Project-CVE-2025-54068

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

⭐ 3🍴 0Aug 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2025-54068

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2025-54068 -u https://target

Template: Laravel Livewire v3 - Remote Command Execution
Severity: critical
Impact: An unauthenticated attacker may execute arbitrary commands in the web server context.
Remediation: Upgrade livewire/livewire to a patched version (>= 3.6.4).

Template by ProjectDiscovery nuclei-templates (flame-11), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact In Livewire v3 (≤ 3.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. ### Patches 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. #