Skip to content
vulnerability

CVE-2025-54068

9.8
Critical
KEV · Exploited in wildEPSS 96%Patch available

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.

exploited
Yes, in CISA KEV since 20 Mar 2026fix by 3 Apr 2026 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 96.3%
Published 17 Jul 2025Analysed here 2 Nov 2026

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: partlyAV · networkCWE-94· Code Injection

Can a WAF block it? Partly. Code injection payloads are often obfuscated, so they slip past generic WAF rules.

Also consider: remove eval sinks · RASP

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2025-54068 being exploited?

Yes. CVE-2025-54068 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-54068?

CVE-2025-54068 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-54068?

Yes. A fix has been recorded for CVE-2025-54068. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-54068 affect?

CVE-2025-54068 affects laravel:livewire. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
laravel:livewire
affected versions
livewire
  • affected>= 3.0.0-beta.1 and < 3.6.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 7 GitHub proofs of concept · 1 Nuclei template

Nuclei
GitHub proofs of concept
+3 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 21 Mar 2026 (SSVC 2.0.3).

timeline

  1. 17 Jul 2025Published
  2. 23 Dec 2025First proof-of-concept repository on GitHub (unvetted) · 158 days (about 5 months) later
  3. 20 Mar 2026Added to CISA KEV (exploited in the wild) · 87 days (about 3 months) later
  4. 21 Mar 2026CISA SSVC assessment: exploitation active · 1 day later
  5. 23 Mar 2026CVE record last updated · 2 days later
  6. 3 Apr 2026CISA remediation due date (US federal agencies) · 10 days later
  7. 2 Nov 2026Analysed by vulneraibility.com · 214 days (about 7 months) later

also known as

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
5 references in the CVE record: 1 advisory, 4 links
  • Advisorythreathunter.ai /blog/iranian-threat-actor-tools-techniques-iocs-ioas/
  • Linkgithub.com /livewire/livewire/security/advisories/GHSA-29cq-5w36-x7w3
  • Linkgithub.com /livewire/livewire/commit/ef04be759da41b14d2d129e670533180a44987dc
  • Linkgithub.com /livewire/livewire/releases/tag/v3.6.4
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-54068

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Nuclei templates: detection templates
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • OSV: advisory aliases and downstream package versions
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved