How severe is GHSA-w98m-2xqg-9cvj?

No CVSS score has been assigned to GHSA-w98m-2xqg-9cvj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w98m-2xqg-9cvj?

GHSA-w98m-2xqg-9cvj affects the following packages: paginator (Hex). Ecosystems affected: Hex.

How do I fix GHSA-w98m-2xqg-9cvj?

Update paginator to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w98m-2xqg-9cvj is resolved across your whole dependency graph.

How do I detect GHSA-w98m-2xqg-9cvj in my Hex dependencies?

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

How do I mitigate GHSA-w98m-2xqg-9cvj 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-w98m-2xqg-9cvj?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w98m-2xqg-9cvj can be triaged on real exposure rather than presence alone.

Is GHSA-w98m-2xqg-9cvj actively exploited in the wild?

No public exploit code has been indexed for GHSA-w98m-2xqg-9cvj 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-w98m-2xqg-9cvj?

GHSA-w98m-2xqg-9cvj has an EPSS (Exploit Prediction Scoring System) score of 3.3%, placing it in the 88th 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-w98m-2xqg-9cvj?

GHSA-w98m-2xqg-9cvj is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-w98m-2xqg-9cvj published, and has it been updated?

GHSA-w98m-2xqg-9cvj was published on April 12, 2022 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💧 Hex

Not in CISA KEV

GHSA-w98m-2xqg-9cvj — paginator

Fix: duffelhq/paginator@bf45e92

GHSA-w98m-2xqg-9cvj is a Code Injection vulnerability in paginator. A fix is available for paginator — see the affected versions and patch details below.

Remote Code Execution in paginator

Also known asCVE-2020-15150

Published

Apr 12, 2022

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

💧paginator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

There is a vulnerability in Paginator which makes it susceptible to Remote Code Execution (RCE) attacks via input parameters to the paginate() function.

Impact

There is a vulnerability in Paginator which makes it susceptible to Remote Code Execution (RCE) attacks via input parameters to the paginate() function. This will potentially affect all current users of Paginator prior to version >= 1.0.0.

Patches

The vulnerability has been patched in version 1.0.0 and all users should upgrade to this version immediately. Note that this patched version uses a dependency that requires an Elixir version >=1.5.

Credits

Thank you to Peter Stöckli.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💧Hex	`paginator`	all versions	1.0.0`mix deps.update paginator`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-w98m-2xqg-9cvj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

There is a vulnerability in Paginator which makes it susceptible to Remote Code Execution (RCE) attacks via input parameters to the `paginate()` function. ### Impact There is a vulnerability in Paginator which makes it susceptible to Remote Code Execution (RCE) attacks via input parameters to the `paginate()` function. This will potentially affect all current users of `Paginator` prior to version >= 1.0.0. ### Patches The vulnerability has been patched in version 1.0.0 and all users should upgrade to this version immediately. Note that this patched version uses a dependency that requires an

O3 Security · Impact-Aware SCA

Is GHSA-w98m-2xqg-9cvj in your dependencies?

O3 Security finds GHSA-w98m-2xqg-9cvj across Hex 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