Bug 2401960 (CVE-2025-61984) - CVE-2025-61984 openssh: OpenSSH: Control characters in usernames can lead to code execution via ProxyCommand
Summary: CVE-2025-61984 openssh: OpenSSH: Control characters in usernames can lead to ...
Keywords:
Status: NEW
Alias: CVE-2025-61984
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2402666 2402667
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-06 19:01 UTC by OSIDB Bzimport
Modified: 2026-06-10 13:48 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:23479 0 None None None 2025-12-17 14:05:51 UTC
Red Hat Product Errata RHSA-2025:23480 0 None None None 2025-12-17 16:33:23 UTC
Red Hat Product Errata RHSA-2025:23481 0 None None None 2025-12-17 17:28:01 UTC
Red Hat Product Errata RHSA-2026:0693 0 None None None 2026-01-15 11:39:19 UTC
Red Hat Product Errata RHSA-2026:0976 0 None None None 2026-01-22 09:03:07 UTC
Red Hat Product Errata RHSA-2026:1678 0 None None None 2026-02-02 08:05:05 UTC
Red Hat Product Errata RHSA-2026:1790 0 None None None 2026-02-03 06:58:29 UTC
Red Hat Product Errata RHSA-2026:1815 0 None None None 2026-02-03 13:22:23 UTC

Description OSIDB Bzimport 2025-10-06 19:01:37 UTC 
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.)
Comment 2 errata-xmlrpc 2025-12-17 14:05:49 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:23479 https://access.redhat.com/errata/RHSA-2025:23479
Comment 3 errata-xmlrpc 2025-12-17 16:33:22 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:23480 https://access.redhat.com/errata/RHSA-2025:23480
Comment 4 errata-xmlrpc 2025-12-17 17:28:00 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2025:23481 https://access.redhat.com/errata/RHSA-2025:23481
Comment 5 errata-xmlrpc 2026-01-15 11:39:18 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:0693 https://access.redhat.com/errata/RHSA-2026:0693
Comment 6 errata-xmlrpc 2026-01-22 09:03:05 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

Via RHSA-2026:0976 https://access.redhat.com/errata/RHSA-2026:0976
Comment 9 errata-xmlrpc 2026-02-02 08:05:03 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:1678 https://access.redhat.com/errata/RHSA-2026:1678
Comment 10 errata-xmlrpc 2026-02-03 06:58:27 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions

Via RHSA-2026:1790 https://access.redhat.com/errata/RHSA-2026:1790
Comment 11 errata-xmlrpc 2026-02-03 13:22:21 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions

Via RHSA-2026:1815 https://access.redhat.com/errata/RHSA-2026:1815
Note You need to log in before you can comment on or make changes to this bug.