Raw response
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3
Host
As of our latest check on 2026-06-08, 217.69.1.109 (The Constant Company, LLC, AS20473, France) had 2 open ports (22, 80) and 53 known CVEs, 2 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-06-08.
CVEs by severity: CRITICAL 8 HIGH 18 MEDIUM 24 LOW 3
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: 95 on a distribution build — the fix may be backported (http_server 2.4.58, openssh 8.9p1). See them
Not counted: 6 only affect another platform (php 8.2.12, http_server 2.4.58). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3
HTTP/1.1 200 OK Server: Apache/2.4.58 (Ubuntu) X-Powered-By: PHP/8.2.12 Content-Type: text/html; charset=utf-8 Content-Length: 189 Date: Mon, 08 Jun 2026 08:40:17 GMT <!doctype html> <html><head><title>Welcome</title><meta name="generator" content="WordPress 6.4.3"></head> <body><h1>Site under maintenance</h1><p>Please check back later.</p></body></html>
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 14 HIGH 42 MEDIUM 28 LOW 11
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.58 · port 80 |
| CVE-2023-28531 CRITICAL 9.8 | openssh 8.9p1 · port 22 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.9p1 · port 22 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 8.9p1 · port 22 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.58 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.58 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.58 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.58 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.58 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.58 · port 80 |
| CVE-2024-6387 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.58 · port 80 |
| CVE-2026-106583 HIGH 7.8 | openssh 8.9p1 · port 22 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-106553 HIGH 7.5 | openssh 8.9p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 8.9p1 · port 22 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-59999 HIGH 7.5 | openssh 8.9p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.9p1 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.58 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.9p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.58 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.58 · port 80 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.9p1 · port 22 |
| CVE-2023-51384 MEDIUM 5.5 | openssh 8.9p1 · port 22 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.58 · port 80 |
| CVE-2024-36387 MEDIUM 5.4 | http_server 2.4.58 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.58 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.9p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.9p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.9p1 · port 22 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.58 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.9p1 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 8.9p1 · port 22 |
| CVE-2025-32728 LOW 3.8 | openssh 8.9p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 8.9p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 8.9p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.9p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 8.9p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 8.9p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 8.9p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 8.9p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 8.9p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 8.9p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.9p1 · port 22 |
These CVEs need a platform this host visibly does not run (for example a flaw of the Windows build on a Linux host). They are not counted. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 2 HIGH 3 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2024-4577 CRITICAL 9.8 known exploited | php 8.2.12 · port 80 |
| CVE-2024-3566 CRITICAL 9.8 | php 8.2.12 · port 80 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-17545 HIGH 7.5 | php 8.2.12 · port 80 |
| CVE-2025-1218 MEDIUM 5.9 | php 8.2.12 · port 80 |
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.