- Server
- SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
- Host key
- ecdsa-sha2-nistp256 f88492c2f3c6581e…
Raw response
SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
Host
Tags: Hosting End-of-life software
As of our latest check on 2026-09-23, 120.26.135.44 (Hangzhou Alibaba Advertising Co.,Ltd., AS37963, China) had 2 open ports (22, 80) and 2 known CVEs, 1 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-09-23.
CVEs by severity: HIGH 1 MEDIUM 1
A match is an indication, not proof: it is based on the software version a service reported, and fixes are often backported without changing the version. See the list
Not counted: 63 on a distribution build — the fix may be backported (openssh 5.9p1). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
HTTP/1.1 200 OK Server: nginx/1.24.0 Date: Wed, 23 Sep 2026 14:25:46 GMT Content-Type: text/html Content-Length: 615 Last-Modified: Sat, 11 May 2024 15:41:02 GMT Connection: keep-alive ETag: "663f918e-267" Accept-Ranges: bytes
These CVEs were matched on software built by an operating-system distribution whose package revision the service does not show. Distributions often fix a flaw without changing the upstream version number, so whether this build is affected cannot be told from its version. They are not counted. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 3 HIGH 20 MEDIUM 29 LOW 11
| CVE | Software |
|---|---|
| CVE-2026-123158 HIGH 8.1 known exploited | openssh 5.9p1 · port 22 |
| CVE-2016-1908 CRITICAL 9.8 | openssh 5.9p1 · port 22 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 5.9p1 · port 22 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 5.9p1 · port 22 |
| CVE-2015-5600 HIGH 8.1 | openssh 5.9p1 · port 22 |
| CVE-2016-0778 HIGH 8.1 | openssh 5.9p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 5.9p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 5.9p1 · port 22 |
| CVE-2015-8325 HIGH 7.8 | openssh 5.9p1 · port 22 |
| CVE-2016-10012 HIGH 7.8 | openssh 5.9p1 · port 22 |
| CVE-2026-106583 HIGH 7.8 | openssh 5.9p1 · port 22 |
| CVE-2010-5107 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2016-10708 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2016-6515 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106553 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2026-59999 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2020-15778 HIGH 7.4 | openssh 5.9p1 · port 22 |
| CVE-2014-1692 HIGH 7.3 | openssh 5.9p1 · port 22 |
| CVE-2016-10009 HIGH 7.3 | openssh 5.9p1 · port 22 |
| CVE-2015-6564 HIGH 7.0 | openssh 5.9p1 · port 22 |
| CVE-2016-10010 HIGH 7.0 | openssh 5.9p1 · port 22 |
| CVE-2019-6109 MEDIUM 6.8 | openssh 5.9p1 · port 22 |
| CVE-2019-6110 MEDIUM 6.8 | openssh 5.9p1 · port 22 |
| CVE-2014-2653 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2016-0777 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2015-6563 MEDIUM 6.4 | openssh 5.9p1 · port 22 |
| CVE-2016-3115 MEDIUM 6.4 | openssh 5.9p1 · port 22 |
| CVE-2016-10011 MEDIUM 6.2 | openssh 5.9p1 · port 22 |
| CVE-2016-6210 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2019-6111 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 5.9p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 5.9p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 5.9p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2017-15906 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2018-15473 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2018-15919 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2018-20685 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 5.9p1 · port 22 |
| CVE-2015-5352 MEDIUM 4.3 | openssh 5.9p1 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 5.9p1 · port 22 |
| CVE-2014-2532 MEDIUM 4.2 | openssh 5.9p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 5.9p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 5.9p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 5.9p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 5.9p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 5.9p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 5.9p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 5.9p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 5.9p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 5.9p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 5.9p1 · port 22 |
Every port that has answered a connection on this address, and when. A port is listed as open above only when a service was identified on it. Times are UTC.