Secuno
ENNL
Book demo

CVE-2025-47913

Go SSH vulnerability

7.5 HIGHPublic exploitEPSS 0.62%
  1. Published13 Nov 2025

Description

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Go SSH< 0.43.0

Remediation

Fixed in
Go SSH≥ 0.43.0

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-394538.3
Navigating to a certain URL on the switch’s web server causes the switch to reboot.…
CVE-2026-633888.4
Libevent is an event notification library. Prior to 2.1.13 and 2.2.2-alpha, libevent…
CVE-2026-507228.1
Libreswan, via the function RSA_authenticate_hash_signature_pkcs1_1_5_rsa(), did not…
CVE-2026-507218.1
Libreswan, via the function RSA_authenticate_hash_signature_raw_rsa(), did not…
CVE-2026-529528.8
In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARN_ON…
CVE-2026-317398.8
In the Linux kernel, the following vulnerability has been resolved: crypto: tegra -…

Frequently asked

Is CVE-2025-47913 being actively exploited?

CVE-2025-47913 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.62%.

How severe is CVE-2025-47913?

CVE-2025-47913 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.62% probability of exploitation.

Which products are affected by CVE-2025-47913?

Affected products include Go SSH.

How do I fix CVE-2025-47913?

Upgrade affected software to a fixed version, for example Go SSH 0.43.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-47913 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 worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

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