CVE-2019-6111

HIGHNVD 5.97.5▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.5 because EPSS predicts 58% probability of exploitation within the next 30 days (top 1.0% of all CVEs). NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 3,999 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 58%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 58%CVSS: 5.9Exploit: ssvc poc · epss top5pct · epss high · public exploitExposed: 3,999

A fix is available — apply it.

An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files/directories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are prevented). A malicious scp server (or Man-in-The-Middle attacker) can overwrite arbitrary files in the scp client target directory. If recursive operation (-r) is performed, the server can manipulate subdirectories as well (for example, to overwrite the .ssh/authorized_keys file).

Live · internet exposure

3,999 internet-exposed hosts are running an affected version of CVE-2019-6111 right now.

across 56 countries (China, United States, Germany, Japan, Singapore)top: openssh
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
5.9
EG Score
7.5(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
Severity75% × 45%
Exploitation65% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
58%
EPSS %ILE
99%
KEV
Not listed

Published

January 31, 2019

Last Modified

December 18, 2025

References (46)

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntussh-krb5 (1:7.2p2-4ubuntu2.7) @ xenial2026-05-27ubuntu
ubuntussh-krb5 (1:7.2p2-4ubuntu2.8) @ xenial2026-05-27ubuntu
redhatopenssh-0:8.0p1-3.el82019-11-05redhat

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 GitHub PoC) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC53n7hu/SNP
    First seen May 12, 2020

    CVE-2019-6111 vulnerability exploitation

    Open source ↗
  • Exploit-DBEDB-46193
    First seen Jan 18, 2019

    SCP Client - Multiple Vulnerabilities (SSHtranger Things)

    Open source ↗
  • Exploit-DBEDB-46516
    First seen Jan 11, 2019

    OpenSSH SCP Client - Write Arbitrary Files

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-6111?
CVE-2019-6111 is a high vulnerability published on January 31, 2019. An issue was discovered in OpenSSH 7.9. Due to the scp implementation being derived from 1983 rcp, the server chooses which files/directories are sent to the client. However, the scp client only performs cursory validation of the object name returned (only directory traversal attacks are…
When was CVE-2019-6111 disclosed?
CVE-2019-6111 was first published in the National Vulnerability Database on January 31, 2019, with the most recent update on December 18, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-6111 actively exploited?
CVE-2019-6111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 58% probability of exploitation in the next 30 days, which ranks it in the top 1.0% of all scored CVEs.
What is the CVSS score of CVE-2019-6111?
CVE-2019-6111 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.5.
How do I remediate CVE-2019-6111?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-6111, 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-2019-6111

Explore →

Is Your Infrastructure Affected by CVE-2019-6111?

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

Start Free Scan →Browse All CVEs