How severe is GHSA-65m9-m259-7jqw?

No CVSS score has been assigned to GHSA-65m9-m259-7jqw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-65m9-m259-7jqw?

GHSA-65m9-m259-7jqw affects the following packages: react-oauth-flow (npm). Ecosystems affected: npm.

How do I fix GHSA-65m9-m259-7jqw?

No patched version of react-oauth-flow has shipped for GHSA-65m9-m259-7jqw yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-65m9-m259-7jqw in my npm dependencies?

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

How do I mitigate GHSA-65m9-m259-7jqw 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-65m9-m259-7jqw actively exploited in the wild?

No public exploit code has been indexed for GHSA-65m9-m259-7jqw 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-65m9-m259-7jqw published, and has it been updated?

GHSA-65m9-m259-7jqw was published on September 3, 2020 and was last updated on October 4, 2021. 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

Improper Authorization in react-oauth-flowGHSA-65m9-m259-7jqw

GHSA-65m9-m259-7jqw is a security vulnerability in react-oauth-flow. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Oct 4, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 4, 2021 · 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.

react-oauth-flownpm

477downloads / week

Description

All versions of react-oauth-flow fail to properly implement the OAuth protocol. The package stores secrets in the front-end code. Instead of using a public OAuth client, it uses a confidential client on the browser. This may allow attackers to compromise server credentials.

Recommendation

No fix is currently available. Consider using an alternative module until a fix is made available.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`react-oauth-flow`	≥ 0.0.0	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-oauth-flow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of react-oauth-flow has shipped for GHSA-65m9-m259-7jqw yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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

All versions of `react-oauth-flow` fail to properly implement the OAuth protocol. The package stores secrets in the front-end code. Instead of using a public OAuth client, it uses a confidential client on the browser. This may allow attackers to compromise server credentials. ## Recommendation No fix is currently available. Consider using an alternative module until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-65m9-m259-7jqw in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works