Which versions of prebid-universal-creative are affected by CVE-2025-59039?

prebid-universal-creative (npm) versions = 1.17.3 is affected.

Is there a fix for CVE-2025-59039?

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

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

Whether CVE-2025-59039 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-59039 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-59039 in prebid-universal-creative

CVE-2025-59039

CVE-2025-59039 is a critical-severity security vulnerability in prebid-universal-creative (npm), affecting versions = 1.17.3. 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

Prebid-universal-creative latest on npm briefly compromised

Workarounds

This has already been unpublished. See Prebid.js 9 release notes for suggestions on moving off the deprecated workflow of using the PUC or pointing to a dynamic version of it. PUC users pointing to latest should transition to 1.17.2 ASAP to avoid similar attacks in the future.

References

https://www.sonatype.com/blog/npm-chalk-and-debug-packages-hit-in-software-supply-chain-attack

Impact

Npm users of PUC 1.17.3 or PUC latest were briefly affected by crypto-related malware detailed in the blog post below. This includes the extremely popular jsdelivr hosting of this file.

Affected versions

prebid-universal-creative (= 1.17.3)

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

We unpublished the version on npm.

Frequently Asked Questions

What is CVE-2025-59039? CVE-2025-59039 is a critical-severity security vulnerability in prebid-universal-creative (npm), affecting versions = 1.17.3. No fixed version is listed yet.
Which versions of prebid-universal-creative are affected by CVE-2025-59039? prebid-universal-creative (npm) versions = 1.17.3 is affected.
Is there a fix for CVE-2025-59039? No fixed version is listed for CVE-2025-59039 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2025-59039 exploitable, and should I be worried? Whether CVE-2025-59039 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-59039 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.