CVE-2025-61984

LOWPre-NVD 3.63.6—
EchelonGraph scoreMEDIUM confidence

Score 3.6 from GitHub Security Advisory (severity: LOW) published 2025-10-06. a secondary CVSS source baseline 3.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
3.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.6Exploit: Elevated riskExposed: 0

A fix is available — apply it.

ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)

CVSS v3
3.6
EG Score
3.6(medium)
EG Risk
32(Track*)
EG Risk 32/100SSVC: Track*

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
Severity36% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

October 6, 2025

Last Modified

July 14, 2026

References (9)

Vendor Advisories for CVE-2025-61984(14)

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

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntussh-askpass-gnome (1:10.0p1-5ubuntu5.1) @ questing2026-05-21ubuntu
ubuntussh-askpass-gnome (1:8.2p1-4ubuntu0.13+esm1) @ focal2026-05-21ubuntu
redhatopenssh-main-10.2p1-9.hum12026-03-23redhat
redhatrhceph/rhceph-7-rhel9:17695084552026-02-03redhat
redhatopenssh-0:8.7p1-13.el9_0.12026-02-03redhat
redhatopenssh-0:8.7p1-30.el9_2.92026-02-03redhat
redhatrhceph/rhceph-8-rhel9:17695123832026-02-02redhat
redhatopenssh-0:9.9p1-7.el10_0.12026-02-02redhat
redhatopenssh-0:8.7p1-38.el9_4.62026-01-22redhat
redhatopenssh-0:8.7p1-45.el9_6.12026-01-15redhat
redhatrhui5/rhua-rhel9:17683770122026-01-15redhat
redhatdiscovery/discovery-server-rhel9:17678889702026-01-08redhat
redhatopenssh-0:8.0p1-27.el8_102025-12-17redhat
redhatopenssh-0:8.7p1-47.el9_72025-12-17redhat
redhatopenssh-0:9.9p1-12.el10_12025-12-17redhat

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

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssh—10.0_p1-r10—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssh—10.1_p1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssh—10.1_p1-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssh1:8.4p1-5 ... 1:8.4p1-5+deb11u6 (7 versions)1:8.4p1-5+deb11u7—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssh1:9.2p1-2 ... 1:9.2p1-2+deb12u7 (8 versions)1:9.2p1-2+deb12u8—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-71:10.0p1-7+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssh1:10.0p1-7, 1:10.0p1-81:10.1p1-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 7× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 153 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCdgl/cve-2025-61984-poc
    First seen Oct 7, 2025

    PoC for OpenSSH ProxyCommand CVE-2025-61984

    Open source ↗

Frequently asked(5)

What is CVE-2025-61984?
CVE-2025-61984 is a low vulnerability published on October 6, 2025. ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration…
When was CVE-2025-61984 disclosed?
CVE-2025-61984 was first published in the National Vulnerability Database on October 6, 2025, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-61984 actively exploited?
CVE-2025-61984 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.5% of all scored CVEs.
What is the CVSS score of CVE-2025-61984?
CVE-2025-61984 has a CVSS v3 base score of 3.6 (NVD).
How do I remediate CVE-2025-61984?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-61984, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-61984?

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

Start Free Scan →Browse All CVEs