What is CVE-2022-25852?

CVE-2022-25852 is a high-severity uncontrolled resource consumption vulnerability in libpq (npm), affecting versions <= 1.8.9. It is fixed in 1.8.10, 3.0.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is CVE-2022-25852?

CVE-2022-25852 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2022-25852?

libpq (npm) versions <= 1.8.9; pg-native (npm) versions <= 3.0.0.

Is there a fix for CVE-2022-25852?

Yes. CVE-2022-25852 is fixed in 1.8.10, 3.0.1. Upgrade to this version or later.

Is CVE-2022-25852 exploitable, and should I be worried?

Whether CVE-2022-25852 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-2022-25852 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-2022-25852?

Upgrade: libpq to 1.8.10 or later, pg-native to 3.0.1 or later.

CVE-2022-25852 in libpq

Q: How severe is CVE-2022-25852?

CVE-2022-25852 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2022-25852?

libpq (npm) versions <= 1.8.9; pg-native (npm) versions <= 3.0.0.

Q: Is there a fix for CVE-2022-25852?

Yes. CVE-2022-25852 is fixed in 1.8.10, 3.0.1. Upgrade to this version or later.

Q: Is CVE-2022-25852 exploitable, and should I be worried?

Whether CVE-2022-25852 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-2022-25852 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-2022-25852?

Upgrade: libpq to 1.8.10 or later, pg-native to 3.0.1 or later.

Summary

pg-native and libpq vulnerable to uncontrolled resource consumption

pg-native before 3.0.1 and libpq before 1.8.10 are vulnerable to Denial of Service (DoS) when the addons attempt to cast the second argument to an array and fail. This happens for every non-array argument passed. Note: pg-native is a mere binding to npm's libpq library, which in turn has the addons and bindings to the actual C libpq library. This means that problems found in pg-native may transitively impact npm's libpq.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2022-25852 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.10, 3.0.1); upgrading removes the vulnerable code path.

Affected versions

libpq (<= 1.8.9) pg-native (<= 3.0.0)

Security releases

libpq → 1.8.10 (npm) pg-native → 3.0.1 (npm)

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

Upgrade the following packages to resolve this vulnerability:

libpq to 1.8.10 or later; pg-native to 3.0.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-25852? CVE-2022-25852 is a high-severity uncontrolled resource consumption vulnerability in libpq (npm), affecting versions <= 1.8.9. It is fixed in 1.8.10, 3.0.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is CVE-2022-25852? CVE-2022-25852 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2022-25852?
- libpq (npm) (versions <= 1.8.9)
- pg-native (npm) (versions <= 3.0.0)
Is there a fix for CVE-2022-25852? Yes. CVE-2022-25852 is fixed in 1.8.10, 3.0.1. Upgrade to this version or later.
Is CVE-2022-25852 exploitable, and should I be worried? Whether CVE-2022-25852 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-2022-25852 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-2022-25852?
- Upgrade libpq to 1.8.10 or later
- Upgrade pg-native to 3.0.1 or later