How severe is GHSA-v69f-5jxm-hwvv?

No CVSS score has been assigned to GHSA-v69f-5jxm-hwvv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v69f-5jxm-hwvv?

GHSA-v69f-5jxm-hwvv affects the following packages: livewire/volt (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-v69f-5jxm-hwvv?

Update livewire/volt to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v69f-5jxm-hwvv is resolved across your whole dependency graph.

How do I detect GHSA-v69f-5jxm-hwvv in my Packagist dependencies?

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

How do I mitigate GHSA-v69f-5jxm-hwvv 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 GHSA-v69f-5jxm-hwvv actively exploited in the wild?

No public exploit code has been indexed for GHSA-v69f-5jxm-hwvv 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 GHSA-v69f-5jxm-hwvv?

GHSA-v69f-5jxm-hwvv has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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 GHSA-v69f-5jxm-hwvv?

GHSA-v69f-5jxm-hwvv is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-v69f-5jxm-hwvv published, and has it been updated?

GHSA-v69f-5jxm-hwvv was published on March 5, 2025 and was last updated on March 5, 2025. 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

Volt Allows RCE Via User-Crafted RequestsGHSA-v69f-5jxm-hwvv

GHSA-v69f-5jxm-hwvv is a Improper Input Validation vulnerability in livewire/volt. A fix is available for livewire/volt — see the affected versions and patch details below.

Also known asCVE-2025-27517

Published

Mar 5, 2025

Updated

Mar 5, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v69f-5jxm-hwvv.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘livewire/volt

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

Volt is an elegantly crafted functional API for Livewire. Malicious, user-crafted request payloads could potentially lead to remote code execution within Volt components. This vulnerability is fixed in 1.7.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`livewire/volt`	all versions	1.7.0`composer require livewire/volt:^1.7.0`

Detection & mitigation playbook

Open-source dependency

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

Malicious, user-crafted request payloads could potentially lead to remote code execution within Volt components.

O3 Security · Impact-Aware SCA

Is GHSA-v69f-5jxm-hwvv in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works