CVE Intelligence
High Memory corruption

CVE-2019-3863 — A flaw was found in libssh2 before 1.8.1. A server could send a multiple keyboard interactive...

A flaw was found in libssh2 before 1.8.1 creating a vulnerability on the SSH client side. A server could send a multiple keyboard interactive response messages whose total length are greater than unsigned char max characters. This value is used by the SSH client as an index to copy memory causing in an out of bounds memory write error.

Published Mar 25, 2019 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 3.4% (30-day exploitation probability)+13
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
3.44%
ahead of 89% of scored CVEs · Oct 14, 2026
Affects
Debian
Debian Linux and 9 more
CVSS base
8.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Libssh2 Libssh2, Netapp Ontap Select Deploy Administration Utility…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Debian Debian Linux version 8.0 Vulnerable NIST National Vulnerability Database
Libssh2 Libssh2 < 1.8.1 Vulnerable NIST National Vulnerability Database
Netapp Ontap Select Deploy Administration Utility versions not specified by the source Vulnerable NIST National Vulnerability Database
Opensuse Leap version 15.0version 42.3 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Desktop version 7.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server version 7.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server Aus version 7.6 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server Eus version 7.6 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server Tus version 7.6 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Workstation version 7.0 Vulnerable NIST National Vulnerability Database
The libssh2 Project Libssh2 version 1.8.1 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.8 CVSS 3.0 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.8 CVSS 3.0 High — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 3.0 High 1.6 5.9 secalert@redhat.com via NIST National Vulnerability Database
7.5 CVSS 3.0 High — — redhat via CVE Program (cve.org) e CISA ADP
6.8 CVSS 2.0 Medium 8.6 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.44%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · the libssh2 project/libssh2
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · libssh2/libssh2, debian/debian linux, netapp/ontap select deploy administration utility, opensuse/leap, redhat/enterpris
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.8
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2019
  • CVE published
    Mar 25, 2019 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

22 on the record

Elsewhere on this site

Debian
every CVE for this vendor
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
  • High CVE-2026-66035 Heap-based Buffer Overflow in Libssh2 Jul 24, 2026
  • High CVE-2026-66034 Out-of-bounds Read in Libssh2 Jul 24, 2026
  • High CVE-2026-66033 Out-of-bounds Read in Libssh2 Jul 24, 2026
  • High CVE-2026-66032 Double Free in Libssh2 Jul 24, 2026
  • Medium CVE-2026-14355 ext/openssl: Memory corruption in openssl_encrypt with AES-WRAP-PAD Jul 3, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2019-3863 is "A flaw was found in libssh2 before 1.8.1. A server could send a multiple keyboard interactive...", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 3.44% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.