CVE-2006-5051

HIGHNVD 8.18.3▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.3 because EPSS predicts 45% probability of exploitation within the next 30 days (top 1.3% of all CVEs). NVD baseline CVSS 8.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 45%CVSS: 8.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Signal handler race condition in OpenSSH before 4.4 allows remote attackers to cause a denial of service (crash), and possibly execute arbitrary code if GSSAPI authentication is enabled, via unspecified vectors that lead to a double-free.

CVSS v3
8.1
EG Score
8.3(high)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

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
Severity83% × 45%
Exploitation45% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
45%
EPSS %ILE
99%
KEV
Not listed

Published

September 27, 2006

Last Modified

April 23, 2026

Advisory Details (6)

Auto-updated Apr 29, 2026
No patch confirmed yet.
generic

About Secunia Research | Flexera

http://secunia.com/advisories/22183
generic

About Secunia Research | Flexera

http://secunia.com/advisories/22173
generic

About Secunia Research | Flexera

http://secunia.com/advisories/22158
generic
http://openssh.org/txt/release-4.4
generic

'Announce: OpenSSH 4.4 released' - MARC

http://marc.info/?l=openssh-unix-dev&m=115939141729160&w=2
generic

FreeBSD Security Advisory FreeBSD-SA-06:22.openssh

http://lists.freebsd.org/pipermail/freebsd-security/2006-October/004051.html

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssh-server (1:3.9p1-1ubuntu2.3) @ hoary2026-05-31ubuntu
redhatopenssh-0:3.9p1-8.RHEL4.172006-09-29redhat
redhatopenssh-0:3.1p1-212006-09-29redhat

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.

Weakness Classification(1)

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

All Vendor Advisories

(3)

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 10× in last 7d / 24× 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.

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

Publicly available exploits

(3 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 PoCanhvutuan/CVE-2024-6387-poc-1
    First seen Oct 22, 2024

    CVE-2024-6387, also known as RegreSSHion, is a high-severity vulnerability found in OpenSSH servers (sshd) running on glibc-based Linux systems. It is a regression of a previously fixed vulnerability (CVE-2006-5051), which means the issue was reintroduced in newer versions of OpenSSH.

    Open source ↗
  • GitHub PoCsardine-web/CVE-2024-6387_Check
    First seen Jul 4, 2024

    A security regression (CVE-2006-5051) was discovered in OpenSSH's server (sshd). There is a race condition which can lead to sshd to handle some signals in an unsafe manner. An unauthenticated, remote attacker may be able to trigger it by failing to authenticate within a set time period.

    Open source ↗
  • GitHub PoCbigb0x/CVE-2024-6387
    First seen Jul 1, 2024

    Bulk Scanning Tool for OpenSSH CVE-2024-6387, CVE-2006-5051 , CVE-2008-4109 and others.

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2006-5051?
CVE-2006-5051 is a high vulnerability published on September 27, 2006. Signal handler race condition in OpenSSH before 4.4 allows remote attackers to cause a denial of service (crash), and possibly execute arbitrary code if GSSAPI authentication is enabled, via unspecified vectors that lead to a double-free.
When was CVE-2006-5051 disclosed?
CVE-2006-5051 was first published in the National Vulnerability Database on September 27, 2006, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-5051 actively exploited?
CVE-2006-5051 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 45% probability of exploitation in the next 30 days, which ranks it in the top 1.3% of all scored CVEs.
What is the CVSS score of CVE-2006-5051?
CVE-2006-5051 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.3.
How do I remediate CVE-2006-5051?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-5051, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2006-5051

Explore →

Is Your Infrastructure Affected by CVE-2006-5051?

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

Start Free Scan →Browse All CVEs