How severe is GHSA-qwvp-268g-jjm8?

No CVSS score has been assigned to GHSA-qwvp-268g-jjm8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qwvp-268g-jjm8?

GHSA-qwvp-268g-jjm8 affects the following packages: livewire/livewire (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qwvp-268g-jjm8?

Update livewire/livewire to 2.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwvp-268g-jjm8 is resolved across your whole dependency graph.

How do I detect GHSA-qwvp-268g-jjm8 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 GHSA-qwvp-268g-jjm8 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 GHSA-qwvp-268g-jjm8?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qwvp-268g-jjm8 can be triaged on real exposure rather than presence alone.

Is GHSA-qwvp-268g-jjm8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qwvp-268g-jjm8 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.

When was GHSA-qwvp-268g-jjm8 published, and has it been updated?

GHSA-qwvp-268g-jjm8 was published on May 15, 2024 and was last updated on November 29, 2024. 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

GHSA-qwvp-268g-jjm8 — livewire/livewire

Fix: livewire/livewire@6929f58

GHSA-qwvp-268g-jjm8 is a security vulnerability in livewire/livewire. A fix is available for livewire/livewire — see the affected versions and patch details below.

Data Leakage Vulnerability in livewire/livewire

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, 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

livewire/livewire versions greater than 2.2.4 and less than 2.2.6 are affected by a data leakage vulnerability. The $this->validate() method, which is expected to return only the validated dataset, was returning all properties of the Livewire component. This regression introduced a security risk, allowing unvalidated data to be exposed, which could lead to unexpected behavior and potential security issues.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`livewire/livewire`	≥ 2.2.5&&< 2.2.6	2.2.6`composer require livewire/livewire:^2.2.6`

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 2.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwvp-268g-jjm8 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qwvp-268g-jjm8 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qwvp-268g-jjm8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

livewire/livewire versions greater than 2.2.4 and less than 2.2.6 are affected by a data leakage vulnerability. The `$this->validate()` method, which is expected to return only the validated dataset, was returning all properties of the Livewire component. This regression introduced a security risk, allowing unvalidated data to be exposed, which could lead to unexpected behavior and potential security issues.

O3 Security · Impact-Aware SCA

Is GHSA-qwvp-268g-jjm8 in your dependencies?

O3 Security finds GHSA-qwvp-268g-jjm8 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works