CVE-2025-47913
Public on
Last Modified:
Description
A flaw in golang.org/x/crypto/ssh/agent causes the SSH agent client to panic when a peer responds with the generic SSH_AGENT_SUCCESS (0x06) message to requests expecting typed replies (e.g., List, Sign). The unmarshal layer produces an unexpected message type, which the client code does not handle, leading to panic("unreachable") or a nil-pointer dereference. A malicious agent or forwarded connection can exploit this to terminate the client process.
Statement
This vulnerability was marked as Important because it allows any malicious or misbehaving SSH agent to force a crash in the client process using a single valid protocol byte. The panic occurs before the client has a chance to validate message structure or recover, which means an attacker controlling—or intercepting—SSH agent traffic can reliably terminate processes that rely on agent interactions. In environments where SSH agents operate over forwarded sockets, shared workspaces, or CI/CD runners, this turns into a reliable, unauthenticated remote denial of service against critical automation or developer tooling. The flaw also stems from unsafe assumptions in the unmarshalling logic, where unexpected but protocol-legal message types drop into “unreachable” code paths instead of being handled gracefully—making it a design-level reliability break rather than a simple error-handling bug. For this reason, it is rated as an important availability-impacting vulnerability rather than a moderate issue.
Mitigation
No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.
Additional information
- This content is not included.Bugzilla 2414943: golang.org/x/crypto/ssh/agent: golang.org/x/crypto/ssh/agent: SSH client panic due to unexpected SSH_AGENT_SUCCESS
- Content from cwe.mitre.org is not included.CWE-241: Improper Handling of Unexpected Data Type
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2025-47913
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2025-47913
Content from github.com is not included.https://github.com/advisories/GHSA-hcg3-q754-cr77
Content from go.dev is not included.https://go.dev/cl/700295
Content from go.dev is not included.https://go.dev/issue/75178
Content from pkg.go.dev is not included.https://pkg.go.dev/vuln/GO-2025-4116
Affected Packages and Issued Red Hat Security Errata
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Red Hat Ceph Storage 7.1 | ceph | Fixed | RHSA-2026:2769 |
| Red Hat Enterprise Linux 10 | buildah | Fixed | RHSA-2026:0436 |
| Red Hat Enterprise Linux 10 | podman | Fixed | RHSA-2026:0545 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | buildah | Fixed | RHSA-2026:14868 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | podman | Fixed | RHSA-2026:5167 |
| Red Hat Enterprise Linux 8 | container-tools:rhel8 | Fixed | RHSA-2026:0753 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | container-tools:rhel8 | Fixed | RHSA-2026:10703 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | container-tools:rhel8 | Fixed | RHSA-2026:19634 |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | container-tools:rhel8 | Fixed | RHSA-2026:10703 |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | container-tools:rhel8 | Fixed | RHSA-2026:19634 |
| No matching records found | |||
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| CVSS v3 Base Score | 7.5 | N/A | 7.5 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality Impact | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
My product is listed as "Out of Support Scope". What does this mean?
Not sure what something means? Check out our Security Glossary.