Which versions of paginator are affected by CVE-2020-15150?

paginator (erlang) versions < 1.0.0 is affected.

Is there a fix for CVE-2020-15150?

Yes. CVE-2020-15150 is fixed in 1.0.0. Upgrade to this version or later.

Is CVE-2020-15150 exploitable, and should I be worried?

Whether CVE-2020-15150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-15150 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2020-15150?

Upgrade paginator to 1.0.0 or later.

CVE-2020-15150 in paginator

Q: Is there a fix for CVE-2020-15150?

Yes. CVE-2020-15150 is fixed in 1.0.0. Upgrade to this version or later.

Q: Is CVE-2020-15150 exploitable, and should I be worried?

Whether CVE-2020-15150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-15150 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-15150?

Upgrade paginator to 1.0.0 or later.

CVE-2020-15150

CVE-2020-15150 is a critical-severity security vulnerability in paginator (erlang), affecting versions < 1.0.0. It is fixed in 1.0.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Remote Code Execution in paginator

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

Credits

Thank you to Peter Stöckli.

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.

Affected versions

paginator (< 1.0.0)

Security releases

paginator → 1.0.0 (erlang)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2020-15150? CVE-2020-15150 is a critical-severity security vulnerability in paginator (erlang), affecting versions < 1.0.0. It is fixed in 1.0.0.
Which versions of paginator are affected by CVE-2020-15150? paginator (erlang) versions < 1.0.0 is affected.
Is there a fix for CVE-2020-15150? Yes. CVE-2020-15150 is fixed in 1.0.0. Upgrade to this version or later.
Is CVE-2020-15150 exploitable, and should I be worried? Whether CVE-2020-15150 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-15150 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-15150? Upgrade paginator to 1.0.0 or later.