CVE-2023-48795

CRITICALNVD 5.99.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 94% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekWeaponized

Also known asEUVD-2023-3093 (ENISA EUVD) · GHSA-45x7-px36-x8w8 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • 3,799 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 or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 94%CVSS: 5.9Exploit: Public PoCExposed services: 3,799

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 chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com 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

3,799 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 72 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
64
EG Risk 64/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation94% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
94%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 5.9 MEDIUM): a likelihood of exploitation, not impact.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
94% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). 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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

December 18, 2023

Last Modified

October 15, 2026

Advisory Details (10)

Auto-updated Jul 14, 2026
Patch available.
Web page

Tags · ronf/asyncssh · GitHub

https://github.com/ronf/asyncssh/tags
Web page

Bitvise SSH Server Version History | Bitvise

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

Commits · openssh/openssh-portable · GitHub

https://github.com/openssh/openssh-portable/commits/master
Web page

OpenSSH: for OpenBSD

https://www.openssh.com/openbsd.html
Web page

Changelog — Paramiko documentation

https://www.paramiko.org/changelog.html
Web page

Xshell Update History – NetSarang Website

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

proftpd/RELEASE_NOTES at master · proftpd/proftpd · GitHub

https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
Web pageMentions a patch (unverified)
https://matt.ucc.asn.au/dropbear/CHANGES

Patch Availability(34)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatceph-2:19.2.1-423.el9cp2026-10-08redhat
redhatrhceph/rhceph-8-rhel9:17911769902026-10-08redhat
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.14.0-202408090010.p0.g3f4aba2.assembly.stream.el92024-08-21redhat
redhatopenshift4/ose-ptp-rhel9:v4.15.0-202408130908.p0.gcb7ef64.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
redhatjenkins-2-plugins-0:4.15.1718879538-1.el82024-07-17redhat
redhatopenshift4/ose-olm-rukpak-rhel8:v4.13.0-202407081338.p0.gaf47118.assembly.stream.el82024-07-17redhat
redhatopenshift4/ose-azure-disk-csi-driver-rhel8:v4.14.0-202407090841.p0.g6d3558a.assembly.stream.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-vsphere-csi-driver-syncer-rhel9:v4.16.0-202406131906.p0.g3cd689f.assembly.stream.el92024-06-27redhat
redhatopenshift4/ose-ptp-rhel9:v4.16.0-202406131906.p0.g4447317.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.12.1716445211-1.el82024-06-05redhat
redhatjenkins-2-plugins-0:4.13.1716445207-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
gogolang.org/x/crypto @ 0.17.0 (fixes >= 0.1.0, < 0.17.0)—ghsa
gogolang.org/x/crypto @ 0.0.0-20231218163308-9d2ee975ef9f (fixes < 0.0.0-20231218163308-9d2ee975ef9f)—ghsa
pipparamiko @ 3.4.0 (fixes >= 2.5.0, < 3.4.0)—ghsa
rustrussh @ 0.40.2 (fixes < 0.40.2)—ghsa

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(2)

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 18× in last 7d / 61× 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 97 of 168 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 71 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (1 GitHub PoC), as are 1 Nuclei detection template, 2 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub checkeroseasfr/Scanner_CVE_OpenSSH
    Published 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 checkerTrixSec/CVE-2023-48795
    Published 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
    Published 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
    Published Apr 16, 2024

    OpenSSH Terrapin Attack - Detection

    Open source ↗

Frequently asked(5)

What is CVE-2023-48795?
CVE-2023-48795 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2023-48795 published?
The CVE record for CVE-2023-48795 was published on December 18, 2023. 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2023-48795 actively exploited?
CVE-2023-48795 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. 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 base score of 5.9 (NVD). EchelonGraph synthesises NVD + 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.