- Server
- SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
- Host key
- ssh-ed25519 d829548611dcfc7a…
Raw response
SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
Host
80.244.13.47
Tags: Hosting
As of our latest check on 2026-05-23, 80.244.13.47 (GlobalTeleHost Corp., AS20724, Netherlands) had 1 open port (22) and 2 known CVEs.
Known CVEs on this host
1open port
0names pointing here
2known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-05-23.
CVEs by severity: MEDIUM 1 LOW 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: 52 from an older observation (http_server 2.4.52; matched 2026-06-08). See them
Not counted: 33 on a distribution build — the fix may be backported (openssh 8.2p1). See them
Not counted: 5 fixed by the distribution (openssh 8.2p1). See them
- Network
- GlobalTeleHost Corp. AS20724
- Open ports
- 22 · at our latest check, 2026-05-23
- Location
- Netherlands NL
- Route
- 80.244.13.0/24 · announced by GlobalTeleHost Corp. AS20724 RPKI valid
- Organisation
- GlobalTeleHost Corp.
- Registry network
- GThost · 80.244.13.0 - 80.244.13.255 · RIPE
- Abuse contact
- [email protected] · for GThost
- First seen
- 2026-05-23 21:56 UTC
- Last seen alive
- 2026-05-23 21:57 UTC
- Hosted domains
- No host name points here
Reputation
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
Services (1)
Vulnerabilities
Distribution build — the fix may be backported (33)
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.
CVEs by severity: CRITICAL 1 HIGH 9 MEDIUM 12 LOW 11
| CVE | Software |
|---|---|
| CVE-2026-60002 CRITICAL 9.4 | openssh 8.2p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.2p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.2p1 · port 22 |
| CVE-2026-106583 HIGH 7.8 | openssh 8.2p1 · port 22 |
| CVE-2020-12062 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2026-106553 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2026-59999 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2020-15778 HIGH 7.4 | openssh 8.2p1 · port 22 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 8.2p1 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.2p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.2p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.2p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 8.2p1 · port 22 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.2p1 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 8.2p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 8.2p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 8.2p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 8.2p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.2p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 8.2p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 8.2p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 8.2p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 8.2p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 8.2p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 8.2p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.2p1 · port 22 |
Fixed by the distribution (5)
The distribution's security data says the package revision this service shows already has the fix for these CVEs, or that its build is not affected. They are not counted.
CVEs by severity: CRITICAL 1 HIGH 2 MEDIUM 2
| CVE | Software |
|---|---|
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.2p1 · port 22 |
| CVE-2021-28041 HIGH 7.1 | openssh 8.2p1 · port 22 |
| CVE-2021-41617 HIGH 7.0 | openssh 8.2p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.2p1 · port 22 |
From an older observation (52)
These CVEs were matched on software this host reported in an earlier observation (matched 2026-06-08), not on a port that is open now, and no service of that kind was open at the latest check (2026-05-23). They are not counted above; 1 of them is known to be exploited.
CVEs by severity: CRITICAL 12 HIGH 28 MEDIUM 12
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.52 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.52 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.52 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.52 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.52 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.52 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.52 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.52 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.52 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.52 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.52 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.52 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.52 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.52 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.52 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.52 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.52 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.52 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.52 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.52 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.52 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.52 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.52 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.52 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.52 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.52 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.52 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.52 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.52 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.52 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.52 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.52 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.52 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.52 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.52 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.52 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.52 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.52 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.52 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.52 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.52 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.52 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.52 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.52 |
Port history
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.