A flaw was found in OpenSSH. After compression is negotiated, a compressed payload can expand past the maximum supported packet size because the inflate loop does not stop at that limit. Memory use grows in the process handling that connection.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-110927 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
Reason given by MITRE
CVE-2026-110927 has been marked as a duplicate of CVE-2026-106585.
CVE-2026-110927
✕ Withdrawn — historical dataMEDIUMPre-NVD 4.3
4.3CVSS
- CVSS v3
- 4.3
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- —Not applicable: this CVE ID was withdrawn
Published
October 15, 2026
Last Modified
October 19, 2026
References (3)
- secalert@redhathttps://access.redhat.com/errata/RHSA-2026:82247
- secalert@redhathttps://access.redhat.com/security/cve/CVE-2026-110927
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=2553037
Frequently asked(4)
What is CVE-2026-110927?
CVE-2026-110927 is a rejected CVE ID: its record was withdrawn on October 21, 2026 and no longer describes a vulnerability. Reason given: CVE-2026-110927 has been marked as a duplicate of CVE-2026-106585. Its record names CVE-2026-106585 as the replacement.
When was the CVE record for CVE-2026-110927 published?
The CVE record for CVE-2026-110927 was published on October 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-110927?
CVE-2026-110927 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-110927?
There is nothing to remediate under CVE-2026-110927: it is a rejected (withdrawn) CVE ID and no longer describes a vulnerability. Its record names CVE-2026-106585 as the replacement; act on that CVE instead.