Which versions of web3-core-subscriptions are affected by CVE-2025-57330?

web3-core-subscriptions (npm) versions <= 2.0.0-alpha.1 is affected.

Is there a fix for CVE-2025-57330?

No fixed version is listed for CVE-2025-57330 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2025-57330 exploitable, and should I be worried?

Whether CVE-2025-57330 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-2025-57330 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.

CVE-2025-57330 in web3-core-subscriptions

Q: What is CVE-2025-57330?

CVE-2025-57330 is a low-severity security vulnerability in web3-core-subscriptions (npm), affecting versions <= 2.0.0-alpha.1. No fixed version is listed yet.

Q: Is there a fix for CVE-2025-57330?

No fixed version is listed for CVE-2025-57330 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2025-57330 exploitable, and should I be worried?

Whether CVE-2025-57330 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-2025-57330 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.

CVE-2025-57330

CVE-2025-57330 is a low-severity security vulnerability in web3-core-subscriptions (npm), affecting versions <= 2.0.0-alpha.1. No fixed version is listed yet.

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

web3-core-subscriptions has a Prototype Pollution vulnerability

The web3-core-subscriptions is a package designed to manages web3 subscriptions. A Prototype Pollution vulnerability in the attachToObject function of web3-core-subscriptions version 1.10.4 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.

Impact

Affected versions

web3-core-subscriptions (<= 2.0.0-alpha.1)

Security releases

Not available

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

No fixed version is listed for CVE-2025-57330 yet.

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

Frequently Asked Questions

What is CVE-2025-57330? CVE-2025-57330 is a low-severity security vulnerability in web3-core-subscriptions (npm), affecting versions <= 2.0.0-alpha.1. No fixed version is listed yet.
Which versions of web3-core-subscriptions are affected by CVE-2025-57330? web3-core-subscriptions (npm) versions <= 2.0.0-alpha.1 is affected.
Is there a fix for CVE-2025-57330? No fixed version is listed for CVE-2025-57330 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2025-57330 exploitable, and should I be worried? Whether CVE-2025-57330 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-2025-57330 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.