CVE-2025-47913

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-11-14. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 13, 2025

Last Modified

January 9, 2026

References (4)

Vendor Advisories for CVE-2025-47913(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcontainer-native-virtualization/virt-artifacts-server-rhel9:17788612652026-05-26redhat
redhatcontainer-tools:rhel8-8060020260515174849.ad008a3a2026-05-20redhat
redhatcontainer-tools:rhel8-8080020260427195445.63b345852026-05-13redhat
redhatpodman-2:4.4.1-22.el9_2.92026-05-13redhat
redhatbuildah-1:1.26.11-1.el9_02026-05-11redhat
redhatbuildah-2:1.39.8-1.el10_02026-05-07redhat
redhatcontainer-native-virtualization/virt-artifacts-server-rhel9:17778672432026-05-05redhat
redhatcontainer-native-virtualization/virt-artifacts-server-rhel9:17774764332026-05-04redhat
redhatcontainer-native-virtualization/virt-artifacts-server-rhel9:17776053052026-05-04redhat
redhatbuildah-2:1.33.13-3.el9_4.12026-04-30redhat
redhatbuildah-2:1.39.6-2.el9_62026-04-29redhat
redhatcontainer-tools:rhel8-8060020260422144418.ad008a3a2026-04-27redhat
redhatpodman-2:4.2.0-6.el9_0.62026-04-15redhat
redhatodf4/rook-ceph-rhel9-operator:17745421012026-04-02redhat
redhatpodman-4:4.9.4-20.el9_4.12026-03-23redhat
redhatpodman-6:5.4.0-15.el10_02026-03-19redhat
redhatcontainer-tools:rhel8-8080020260226135022.63b345852026-03-17redhat
redhatbuildah-1:1.29.5-1.el9_2.22026-03-12redhat
redhatquay/quay-rhel8:17730976212026-03-10redhat
redhatopenshift-pipelines/pipelines-cli-tkn-rhel9:17726948652026-03-05redhat
redhatrhosp-rhel8/osp-director-operator:17709099842026-02-23redhat
redhatrhtas/gitsign-rhel9:17707342832026-02-18redhat
redhatceph-2:18.2.1-381.el8cp2026-02-17redhat
redhatrhceph/grafana-rhel9:17706306072026-02-16redhat
redhatdevworkspace/devworkspace-rhel9-operator:17694618432026-02-10redhat
redhatrhtas/gitsign-rhel9:17701081932026-02-05redhat
redhatquay/quay-rhel8:17701465652026-02-04redhat
redhatpodman-5:5.4.0-18.el9_62026-01-26redhat
redhatopenshift-gitops-1/argocd-rhel9:17688245322026-01-22redhat
redhatopenshift-gitops-1/argocd-agent-rhel8:17688817012026-01-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/crypto—
  • every version up to 0.43.0: fixed in 0.43.0
—
golang.org/x/crypto/ssh/agent—
  • every version up to 0.43.0: fixed in 0.43.0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.0~git20201221.eec23a3-1 ... 1:0.53.0-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.10.0-1 ... 1:0.55.0-1 (35 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.25.0-1 ... 1:0.55.0-1 (20 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-go.crypto1:0.25.0-1 ... 1:0.42.0-4 (9 versions)
  • every version up to 1:0.43.0-1: fixed in 1:0.43.0-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(19)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 91 of 180 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-10-12 17:01 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-11 20:35 UTCEG score recompute
  7. 2026-10-11 18:46 UTCEG score recompute
  8. 2026-10-11 15:22 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-02 00:40 UTCOSV refresh
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-09-27 13:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.6% · 47th percentile
Show 66 more
  1. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-09-21 21:06 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-09-12 18:00 UTCOSV refresh
  9. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  26. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  27. 2026-08-24 23:14 UTCOSV refresh
  28. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  29. 2026-08-24 09:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  30. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  32. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  33. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  34. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  35. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  37. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  38. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  39. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  40. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  41. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  42. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  43. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  44. 2026-08-08 16:49 UTCOSV refresh
  45. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  47. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  48. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  49. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  50. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  51. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  52. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  53. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  54. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  56. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  57. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  58. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  59. 2026-07-23 15:11 UTCOSV refresh
  60. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  61. 2026-07-23 02:57 UTCEG score recompute
  62. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  63. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  64. 2026-07-20 17:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  65. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  66. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.6% · 46th percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-47913?
CVE-2025-47913 is a high-severity vulnerability; its CVE record was published on November 13, 2025. SSH clients receiving SSHAGENTSUCCESS when expecting a typed response will panic and cause early termination of the client process.
When was the CVE record for CVE-2025-47913 published?
The CVE record for CVE-2025-47913 was published on November 13, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 9, 2026; the record at its source may have been updated since.
Is CVE-2025-47913 actively exploited?
CVE-2025-47913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-47913?
CVE-2025-47913 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-47913?
A fix for CVE-2025-47913 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-47913 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-47913

Explore →

Is Your Infrastructure Affected by CVE-2025-47913?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs