How severe is GHSA-6wjw-qf87-fv5v?

No CVSS score has been assigned to GHSA-6wjw-qf87-fv5v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6wjw-qf87-fv5v?

GHSA-6wjw-qf87-fv5v affects the following packages: illuminate/encryption (Packagist), illuminate/encryption (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6wjw-qf87-fv5v?

Update illuminate/encryption to 5.5.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wjw-qf87-fv5v is resolved across your whole dependency graph.

How do I detect GHSA-6wjw-qf87-fv5v in my Packagist dependencies?

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

How do I mitigate GHSA-6wjw-qf87-fv5v 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-6wjw-qf87-fv5v?

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

Is GHSA-6wjw-qf87-fv5v actively exploited in the wild?

No public exploit code has been indexed for GHSA-6wjw-qf87-fv5v 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-6wjw-qf87-fv5v published, and has it been updated?

GHSA-6wjw-qf87-fv5v 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-6wjw-qf87-fv5v — illuminate/encryption

Fix: illuminate/encryption@51667a5

GHSA-6wjw-qf87-fv5v is a security vulnerability in illuminate/encryption. A fix is available for illuminate/encryption — see the affected versions and patch details below.

Laravel Encrypter Failure to decryption vulnerability

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘illuminate/encryption🐘illuminate/encryption

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

A potential exploit of the Laravel Encrypter component that may cause the Encrypter to fail on decryption and unexpectedly return false.

To exploit this, the attacker must be able to modify the encrypted payload before it is decrypted. Depending on the code within your application, this could lead to unexpected behavior when combined with weak type comparisons, for example:

<?php

$decyptedValue = decrypt($secret);

if ($decryptedValue == '') {
    // Code is run even though decrypted value is false...
}

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`illuminate/encryption`	≥ 5.5.0&&< 5.5.40	5.5.40`composer require illuminate/encryption:^5.5.40`
🐘Packagist	`illuminate/encryption`	≥ 5.6.0&&< 5.6.15	5.6.15`composer require illuminate/encryption:^5.6.15`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for illuminate/encryption, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update illuminate/encryption to 5.5.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wjw-qf87-fv5v 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-6wjw-qf87-fv5v can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6wjw-qf87-fv5v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A potential exploit of the Laravel Encrypter component that may cause the Encrypter to fail on decryption and unexpectedly return false. To exploit this, the attacker must be able to modify the encrypted payload before it is decrypted. Depending on the code within your application, this could lead to unexpected behavior when combined with weak type comparisons, for example: ```php <?php $decyptedValue = decrypt($secret); if ($decryptedValue == '') { // Code is run even though decrypted value is false... } ```

O3 Security · Impact-Aware SCA

Is GHSA-6wjw-qf87-fv5v in your dependencies?

O3 Security finds GHSA-6wjw-qf87-fv5v 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