How severe is GHSA-x565-32qp-m3vf?

GHSA-x565-32qp-m3vf has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-x565-32qp-m3vf?

GHSA-x565-32qp-m3vf affects the following packages: phin (npm). Ecosystems affected: npm.

How do I fix GHSA-x565-32qp-m3vf?

Update phin to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x565-32qp-m3vf is resolved across your whole dependency graph.

How do I detect GHSA-x565-32qp-m3vf in my npm dependencies?

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

How do I mitigate GHSA-x565-32qp-m3vf 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-x565-32qp-m3vf actively exploited in the wild?

No public exploit code has been indexed for GHSA-x565-32qp-m3vf 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-x565-32qp-m3vf published, and has it been updated?

GHSA-x565-32qp-m3vf was published on April 11, 2024 and was last updated on April 11, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

phin may include sensitive headers in subsequent requests after redirectGHSA-x565-32qp-m3vf

MEDIUMFix: ethanent/phin@c071f95

GHSA-x565-32qp-m3vf is a medium-severity (CVSS 4.3) vulnerability in phin. A fix is available for phin — see the affected versions and patch details below.

Published

Apr 11, 2024

Updated

Apr 11, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 11, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

phinnpm

2.6Mdownloads / week

Description

Impact

Users may be impacted if sending requests including sensitive data in specific headers with followRedirects enabled.

Patches

The follow-redirects library is now being used for redirects and removes some headers that may contain sensitive information in some situations.

Workarounds

N/A. Please update to resolve the issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`phin`	all versions	3.7.1`npm install phin@3.7.1`

Detection & mitigation playbook

Open-source dependency

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

### Impact Users may be impacted if sending requests including sensitive data in specific headers with `followRedirects` enabled. ### Patches The [follow-redirects](https://github.com/follow-redirects/follow-redirects) library is now being used for redirects and removes some headers that may contain sensitive information in some situations. ### Workarounds N/A. Please update to resolve the issue.

O3 Security · Impact-Aware SCA

Is GHSA-x565-32qp-m3vf in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works