How severe is CVE-2025-3757?

No CVSS score has been assigned to CVE-2025-3757 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-3757?

CVE-2025-3757 affects the following packages: github.com/openpubkey/openpubkey (Go). Ecosystems affected: Go.

How do I fix CVE-2025-3757?

Update github.com/openpubkey/openpubkey to 0.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-3757 is resolved across your whole dependency graph.

How do I detect CVE-2025-3757 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openpubkey/openpubkey, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-3757 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-3757 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-3757 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-3757?

CVE-2025-3757 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-3757?

CVE-2025-3757 is classified as CWE-305 (CWE-305), CWE-347 (CWE-347). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-3757 published, and has it been updated?

CVE-2025-3757 was published on May 13, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2025-3757 — openpubkey

CVE-2025-3757 is a CWE-305 vulnerability in github.com/openpubkey/openpubkey. A fix is available for github.com/openpubkey/openpubkey — see the affected versions and patch details below.

Authentication Bypass in OpenPubKey

Also known asGHSA-537f-gxgm-3jjqGO-2025-3679

Published

May 13, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-3757.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/openpubkey/openpubkey

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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

Patches

Upgrade to v0.10.0 or greater. This vulnerability is not present in versions of OpenPubkey after v0.9.0.

References

CVE-2025-3757

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/openpubkey/openpubkey`	all versions	0.10.0`go get github.com/openpubkey/openpubkey@v0.10.0`

Affected Products

1 product · 1 configurations

Application

openpubkeyopenpubkey

< 0.10.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openpubkey/openpubkey, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openpubkey/openpubkey to 0.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-3757 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Versions of OpenPubkey library prior to 0.10.0 contained a vulnerability that would allow a specially crafted JWS to bypass signature verification. ### Patches Upgrade to v0.10.0 or greater. This vulnerability is not present in versions of OpenPubkey after v0.9.0. ### References [CVE-2025-3757 ](https://www.cve.org/CVERecord?id=CVE-2025-3757)

O3 Security · Impact-Aware SCA

Is CVE-2025-3757 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works