CVE-2023-48795

CRITICALPre-NVD 5.99.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 94% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.9 retained for reference (NVD's own analysis pending). Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: cisa-adp, epss
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 13,092 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • High exploitation likelihood — EPSS 94%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 94%CVSS: 5.9Exploit: ssvc poc · epss top5pct · epss high · public exploitExposed services: 13,092

A fix is available — apply it.

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in [email protected] and (if CBC is used) the [email protected] MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.

Internet exposure · derived from Shodan data

13,092 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2023-48795, in our KEV-Exposure radar’s Shodan-derived sample.

across 88 countries (China, United States, Germany, France, Netherlands)top: openssh
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
5.9
EG Score
9.0CRITICALhigh confidence
EG Risk
78
EG Risk 78/100CISA SSVC

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
Severity90% × 45%
Exploitation94% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
94%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 18, 2023

Last Modified

July 14, 2026

Advisory Details (10)

Auto-updated Jul 14, 2026
⚠️ Active exploitation confirmed. Patch available.
generic

Tags · ronf/asyncssh · GitHub

https://github.com/ronf/asyncssh/tags
generic

Bitvise SSH Server Version History | Bitvise

https://www.bitvise.com/ssh-server-version-history
generic

Commits · openssh/openssh-portable · GitHub

https://github.com/openssh/openssh-portable/commits/master
generic

OpenSSH: for OpenBSD

https://www.openssh.com/openbsd.html
generic🟡 PoC Available

Changelog — Paramiko documentation

https://www.paramiko.org/changelog.html
generic

Xshell Update History – NetSarang Website

https://www.netsarang.com/en/xshell-update-history/
generic

proftpd/RELEASE_NOTES at master · proftpd/proftpd · GitHub

https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
genericMentions a patch (unverified)🔴 Active Exploitation
https://matt.ucc.asn.au/dropbear/CHANGES

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatoath-toolkit-0:2.6.12-1.el8cp2025-05-07redhat
redhatopenshift4/ose-installer:v4.14.0-202410120808.p0.gb6457e9.assembly.stream.el82024-10-23redhat
redhatopenshift4/ose-docker-builder-rhel9:v4.17.0-202409122005.p1.gcfcf3bd.assembly.stream.el92024-10-01redhat
redhatopenshift4/ose-tools-rhel8:v4.14.0-202408260910.p0.g44b3ac2.assembly.stream.el82024-09-11redhat
redhatopenshift4/egress-router-cni-rhel8:v4.14.0-202408070332.p0.g96f2f54.assembly.stream.el82024-08-22redhat
redhatopenshift4/ose-ptp-rhel9:v4.15.0-202408130908.p0.gcb7ef64.assembly.stream.el92024-08-21redhat
redhatopenshift4/ose-ptp-rhel9:v4.14.0-202408090010.p0.g3f4aba2.assembly.stream.el92024-08-21redhat
redhatopenshift4/ose-olm-rukpak-rhel8:v4.12.0-202408072016.p0.gf219ce7.assembly.stream.el82024-08-19redhat
redhatopenshift4/ose-aws-ebs-csi-driver-rhel8:v4.14.0-202407120139.p0.g4622dee.assembly.stream.el82024-08-07redhat
redhatopenshift4/egress-router-cni-rhel8:v4.15.0-202407302337.p0.gf8ec690.assembly.stream.el82024-08-07redhat
redhatopenshift4/ose-aws-efs-csi-driver-container-rhel8:v4.14.0-202407120139.p0.g18d04fd.assembly.stream.el82024-08-07redhat
redhatopenshift4/egress-router-cni-rhel9:v4.16.0-202407180206.p0.g7089efe.assembly.stream.el92024-07-24redhat
redhatcontainer-native-virtualization/cluster-network-addons-operator-rhel9:v4.15.3-72024-07-18redhat
redhatopenshift4/ose-azure-disk-csi-driver-rhel8:v4.14.0-202407090841.p0.g6d3558a.assembly.stream.el82024-07-17redhat
redhatopenshift4/ose-olm-rukpak-rhel8:v4.13.0-202407081338.p0.gaf47118.assembly.stream.el82024-07-17redhat
redhatjenkins-2-plugins-0:4.15.1718879538-1.el82024-07-17redhat
redhatopenshift4/ose-vsphere-cluster-api-controllers-rhel8:v4.14.0-202407021509.p0.gb5346ad.assembly.stream.el82024-07-11redhat
redhatopenshift4/ose-installer-artifacts:v4.15.0-202406251908.p0.g132530d.assembly.stream.el82024-07-02redhat
redhatopenshift4/ose-ptp-rhel9:v4.16.0-202406131906.p0.g4447317.assembly.stream.el92024-06-27redhat
redhatopenshift4/ose-vsphere-csi-driver-syncer-rhel9:v4.16.0-202406131906.p0.g3cd689f.assembly.stream.el92024-06-27redhat
redhatopenshift4/ose-olm-rukpak-rhel8:v4.14.0-202406180839.p0.gc9409c6.assembly.stream.el82024-06-26redhat
redhatpodman-3:4.4.1-14.4.rhaos4.14.el82024-06-19redhat
redhatjenkins-2-plugins-0:4.14.1716388016-1.el82024-06-05redhat
redhatjenkins-2-plugins-0:4.13.1716445207-1.el82024-06-05redhat
redhatjenkins-2-plugins-0:4.12.1716445211-1.el82024-06-05redhat
redhatrhosp-rhel8/osp-director-operator-bundle:1.3.0-262024-05-29redhat
redhatrhosp-rhel9/osp-director-operator-bundle:1.3.1-272024-05-29redhat
redhatpython-paramiko-0:2.11.0-2.el8ost2024-05-22redhat
redhatcontainer-tools:rhel8-8100020240227110532.828888972024-05-22redhat
redhatpython-paramiko-0:2.11.0-2.el9ost2024-05-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

(50 across 14 ecosystems)
Debian:13(6)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-4: fixed in 2022.83-4
—
erlang—
  • every version up to 1:25.3.2.8+dfsg-1: fixed in 1:25.3.2.8+dfsg-1
—
filezilla—
  • every version up to 3.66.4-1: fixed in 3.66.4-1
—
golang-go.crypto—
  • every version up to 1:0.17.0-1: fixed in 1:0.17.0-1
—
libssh—
  • every version up to 0.10.6-1: fixed in 0.10.6-1
—
libssh2—
  • every version up to 1.11.0-4: fixed in 1.11.0-4
—
Debian:14(6)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-4: fixed in 2022.83-4
—
erlang—
  • every version up to 1:25.3.2.8+dfsg-1: fixed in 1:25.3.2.8+dfsg-1
—
filezilla—
  • every version up to 3.66.4-1: fixed in 3.66.4-1
—
golang-go.crypto—
  • every version up to 1:0.17.0-1: fixed in 1:0.17.0-1
—
libssh—
  • every version up to 0.10.6-1: fixed in 0.10.6-1
—
libssh2—
  • every version up to 1.11.0-4: fixed in 1.11.0-4
—
Debian:11(5)
PackageVulnerable rangeFix by version rangeDependents
dropbear2020.81-3
  • every version up to 2020.81-3+deb11u1: fixed in 2020.81-3+deb11u1
—
erlang1:23.2.6+dfsg-1, 1:23.2.6+dfsg-1+deb11u1
  • every version up to 1:23.2.6+dfsg-1+deb11u2: fixed in 1:23.2.6+dfsg-1+deb11u2
—
filezilla3.52.2-3
  • every version up to 3.52.2-3+deb11u1: fixed in 3.52.2-3+deb11u1
—
golang-go.crypto1:0.0~git20201221.eec23a3-1 ... 1:0.53.0-1 (40 versions)
  • every version on: no fix on record
—
libssh0.9.5-1, 0.9.5-1+deb11u1, 0.9.6-1, 0.9.6-2, 0.9.7-0+deb11u1
  • every version up to 0.9.8-0+deb11u1: fixed in 0.9.8-0+deb11u1
—
Debian:12(5)
PackageVulnerable rangeFix by version rangeDependents
dropbear2022.83-1, 2022.83-1+deb12u1~bpo11+1
  • every version up to 2022.83-1+deb12u1: fixed in 2022.83-1+deb12u1
—
erlang1:25.2.3+dfsg-1
  • every version up to 1:25.2.3+dfsg-1+deb12u1: fixed in 1:25.2.3+dfsg-1+deb12u1
—
filezilla3.63.0-1, 3.63.0-1+deb12u1, 3.63.0-1+deb12u2
  • every version up to 3.63.0-1+deb12u3: fixed in 3.63.0-1+deb12u3
—
golang-go.crypto1:0.10.0-1 ... 1:0.56.0-1 (36 versions)
  • every version on: no fix on record
—
libssh0.10.5-2, 0.10.5-3, 0.10.5-3+hurd.1
  • every version up to 0.10.6-0+deb12u1: fixed in 0.10.6-0+deb12u1
—
Alpine:v3.16(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.82-r2: fixed in 2022.82-r2
—
libssh2—
  • every version up to 1.11.0-r0: fixed in 1.11.0-r0
—
openssh—
  • every version up to 9.0_p1-r5: fixed in 9.0_p1-r5
—
Alpine:v3.17(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-r1: fixed in 2022.83-r1
—
libssh2—
  • every version up to 1.11.0-r0: fixed in 1.11.0-r0
—
openssh—
  • every version up to 9.1_p1-r5: fixed in 9.1_p1-r5
—
Alpine:v3.18(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-r2: fixed in 2022.83-r2
—
libssh2—
  • every version up to 1.11.0-r0: fixed in 1.11.0-r0
—
openssh—
  • every version up to 9.3_p2-r1: fixed in 9.3_p2-r1
—
Alpine:v3.19(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-r4: fixed in 2022.83-r4
—
libssh2—
  • every version up to 1.11.0-r1: fixed in 1.11.0-r1
—
openssh—
  • every version up to 9.6_p1-r0: fixed in 9.6_p1-r0
—
Alpine:v3.20(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-r4: fixed in 2022.83-r4
—
libssh2—
  • every version up to 1.11.0-r1: fixed in 1.11.0-r1
—
openssh—
  • every version up to 9.6_p1-r0: fixed in 9.6_p1-r0
—
Alpine:v3.21(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-r4: fixed in 2022.83-r4
—
libssh2—
  • every version up to 1.11.0-r1: fixed in 1.11.0-r1
—
openssh—
  • every version up to 9.6_p1-r0: fixed in 9.6_p1-r0
—
Alpine:v3.22(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-r4: fixed in 2022.83-r4
—
libssh2—
  • every version up to 1.11.0-r1: fixed in 1.11.0-r1
—
openssh—
  • every version up to 9.6_p1-r0: fixed in 9.6_p1-r0
—
Alpine:v3.23(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-r4: fixed in 2022.83-r4
—
libssh2—
  • every version up to 1.11.0-r1: fixed in 1.11.0-r1
—
openssh—
  • every version up to 9.6_p1-r0: fixed in 9.6_p1-r0
—
Alpine:v3.24(3)
PackageVulnerable rangeFix by version rangeDependents
dropbear—
  • every version up to 2022.83-r4: fixed in 2022.83-r4
—
libssh2—
  • every version up to 1.11.0-r1: fixed in 1.11.0-r1
—
openssh—
  • every version up to 9.6_p1-r0: fixed in 9.6_p1-r0
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/crypto—
  • 0.1.0 up to 0.17.0: fixed in 0.17.0
  • every version up to 0.0.0-20231218163308-9d2ee975ef9f: fixed in 0.0.0-20231218163308-9d2ee975ef9f
  • every version up to 0.17.0: fixed in 0.17.0
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 1× in last 7d / 14× 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 111 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

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

  • GitHub PoCoseasfr/Scanner_CVE_OpenSSH
    First seen May 21, 2026

    Scanner para identificação de servidores com softwares SSH possivelmente vulnerável às CVEs CVE-2024-6387 e CVE-2023-48795.

    Open source ↗
  • GitHub PoCTrixSec/CVE-2023-48795
    First seen Jan 8, 2025

    A Python-based tool to check for vulnerabilities in OpenSSH installations on local or remote systems by scanning specific IPs. It checks if the OpenSSH version is affected by CVE-2023-48795

    Open source ↗
  • GitHub PoCkabiri-labs/sshfinder
    First seen Dec 5, 2024

    Fast, parallel SSH discovery and security auditing across hosts and CIDR ranges: identifies SSH on any port in real time, then flags auth methods, weak crypto, Terrapin (CVE-2023-48795), and reused host keys.

    Open source ↗
  • Nucleijavascript/cves/2023/CVE-2023-48795.yaml
    First seen Jan 1, 2023

    OpenSSH Terrapin Attack - Detection

    Open source ↗

Frequently asked(5)

What is CVE-2023-48795?
CVE-2023-48795 is a critical vulnerability published on December 18, 2023. The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a…
When was CVE-2023-48795 disclosed?
CVE-2023-48795 was first published on December 18, 2023, 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-2023-48795 actively exploited?
CVE-2023-48795 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 94% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-48795?
CVE-2023-48795 has a CVSS v3.1 base score of 5.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-48795?
A fix for CVE-2023-48795 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-48795 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-2023-48795

Explore →

Is Your Infrastructure Affected by CVE-2023-48795?

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