How severe is GHSA-rvg8-pwq2-xj7q?

No CVSS score has been assigned to GHSA-rvg8-pwq2-xj7q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rvg8-pwq2-xj7q?

GHSA-rvg8-pwq2-xj7q affects the following packages: base64url (npm). Ecosystems affected: npm.

How do I fix GHSA-rvg8-pwq2-xj7q?

Update base64url to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvg8-pwq2-xj7q is resolved across your whole dependency graph.

How do I detect GHSA-rvg8-pwq2-xj7q in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for base64url. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rvg8-pwq2-xj7q 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-rvg8-pwq2-xj7q?

O3 pinpoints whether GHSA-rvg8-pwq2-xj7q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rvg8-pwq2-xj7q actively exploited in the wild?

No public exploit code has been indexed for GHSA-rvg8-pwq2-xj7q 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-rvg8-pwq2-xj7q published, and has it been updated?

GHSA-rvg8-pwq2-xj7q was published on September 1, 2020 and was last updated on September 24, 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

GHSA-rvg8-pwq2-xj7q

Fix: brianloveswords/base64url#25

GHSA-rvg8-pwq2-xj7q is a security vulnerability in base64url. O3 Security confirms whether GHSA-rvg8-pwq2-xj7q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Out-of-bounds Read in base64url

Published

Sep 1, 2020

Updated

Sep 24, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 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, and reverse-dependency count shows how many other packages break if it stays unpatched.

1Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

base64urlnpm

6.9Mdownloads / week

Description

Versions of base64url before 3.0.0 are vulnerable to to out-of-bounds reads as it allocates uninitialized Buffers when number is passed in input on Node.js 4.x and below.

Recommendation

Update to version 3.0.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`base64url`	all versions	3.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for base64url. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update base64url to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvg8-pwq2-xj7q 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 pinpoints whether GHSA-rvg8-pwq2-xj7q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rvg8-pwq2-xj7q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `base64url` before 3.0.0 are vulnerable to to out-of-bounds reads as it allocates uninitialized Buffers when number is passed in input on Node.js 4.x and below. ## Recommendation Update to version 3.0.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-rvg8-pwq2-xj7q in your dependencies?

O3 detects GHSA-rvg8-pwq2-xj7q across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works