Which versions of github.com/openpubkey/openpubkey are affected by CVE-2025-3757?

github.com/openpubkey/openpubkey (go) versions < 0.10.0 is affected.

Is there a fix for CVE-2025-3757?

Yes. CVE-2025-3757 is fixed in 0.10.0. Upgrade to this version or later.

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

Whether CVE-2025-3757 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-3757 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-2025-3757?

Upgrade github.com/openpubkey/openpubkey to 0.10.0 or later.

CVE-2025-3757 in github.com/openpubkey/openpubkey

Q: What is CVE-2025-3757?

CVE-2025-3757 is a critical-severity security vulnerability in github.com/openpubkey/openpubkey (go), affecting versions < 0.10.0. It is fixed in 0.10.0.

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

Yes. CVE-2025-3757 is fixed in 0.10.0. Upgrade to this version or later.

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

Whether CVE-2025-3757 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-3757 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-2025-3757?

Upgrade github.com/openpubkey/openpubkey to 0.10.0 or later.

CVE-2025-3757

CVE-2025-3757 is a critical-severity security vulnerability in github.com/openpubkey/openpubkey (go), affecting versions < 0.10.0. It is fixed in 0.10.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

OpenPubkey Vulnerable to Authentication Bypass

References

CVE-2025-3757

Impact

Versions of OpenPubkey library prior to 0.10.0 contained a vulnerability that would allow a specially crafted JWS to bypass signature verification.

Affected versions

github.com/openpubkey/openpubkey (< 0.10.0)

Security releases

github.com/openpubkey/openpubkey → 0.10.0 (go)

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 to v0.10.0 or greater. This vulnerability is not present in versions of OpenPubkey after v0.9.0.

Frequently Asked Questions

What is CVE-2025-3757? CVE-2025-3757 is a critical-severity security vulnerability in github.com/openpubkey/openpubkey (go), affecting versions < 0.10.0. It is fixed in 0.10.0.
Which versions of github.com/openpubkey/openpubkey are affected by CVE-2025-3757? github.com/openpubkey/openpubkey (go) versions < 0.10.0 is affected.
Is there a fix for CVE-2025-3757? Yes. CVE-2025-3757 is fixed in 0.10.0. Upgrade to this version or later.
Is CVE-2025-3757 exploitable, and should I be worried? Whether CVE-2025-3757 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-3757 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-2025-3757? Upgrade github.com/openpubkey/openpubkey to 0.10.0 or later.