CVE-2025-4658

Openpubkey vulnerability

9.8 CRITICALEPSS 0.34%

Published13 May 2025

Description

Versions of OpenPubkey library prior to 0.10.0 contained a vulnerability that would allow a specially crafted JWS to bypass signature verification. As OPKSSH depends on the OpenPubkey library for authentication, this vulnerability in OpenPubkey also applies to OPKSSH versions prior to 0.5.0 and would allow an attacker to bypass OPKSSH authentication.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Openpubkey< 0.10.0

Openpubkey Opkssh< 0.5.0

Remediation

Fixed in

Openpubkey≥ 0.10.0

Openpubkey Opkssh≥ 0.5.0

Frequently asked

Is CVE-2025-4658 being actively exploited?

CVE-2025-4658 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.34%.

How severe is CVE-2025-4658?

CVE-2025-4658 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.34% probability of exploitation.

Which products are affected by CVE-2025-4658?

Affected products include Openpubkey, Openpubkey Opkssh.

How do I fix CVE-2025-4658?

Upgrade affected software to a fixed version, for example Openpubkey 0.10.0, Openpubkey Opkssh 0.5.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-4658 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.