CVE-2026-45843VulnerabilityPublished 2 May 2026Updated 9 Jun 2026

Microsoft · slip: bound decode() reads against the compressed packet length

Affects MicrosoftSource GCVE Database

Compare

Authoritative record:CVE-2026-45843· High 8.2

Not known to be exploited · CVSS 8.2 High · fixed in d42bec6e4f6d6d658be365539400b3314b76b2a7 : patch Microsoft soon.

Data as of 30 Oct 2026, 11:34 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in d42bec6e4f6d6d658be365539400b3314b76b2a7, 335957df4ed60f02a2ec0432fbedbf0cc7241d8b, 37537e42e6df387398bee85cb85070cc80bb1e10 +5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

microsoft-security-response-ce

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < d42bec6e4f6d6d658be365539400b3314b76b2a7	Fixed in d42bec6e4f6d6d658be365539400b3314b76b2a7
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 335957df4ed60f02a2ec0432fbedbf0cc7241d8b	Fixed in 335957df4ed60f02a2ec0432fbedbf0cc7241d8b
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 37537e42e6df387398bee85cb85070cc80bb1e10	Fixed in 37537e42e6df387398bee85cb85070cc80bb1e10
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 6268f01ae989013671b526c883e92655342c6f6f	Fixed in 6268f01ae989013671b526c883e92655342c6f6f
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 0511ecb00e61bf28e2fec4bb41fcce385c3a3b2d	Fixed in 0511ecb00e61bf28e2fec4bb41fcce385c3a3b2d
LinuxLinux	Affected ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 9aafba2f49e1fcccc2018816f5836a609c925879	Fixed in 9aafba2f49e1fcccc2018816f5836a609c925879

Description

CVE-2026-45843 is a vulnerability identified by the Microsoft Security Response Center involving the slip protocol where the decode() function reads beyond the compressed packet length. The available information does not provide detailed technical specifics or exploitation data. There is no CVSS score assigned to this vulnerability, and no known exploits in the wild have been reported. The affected products include Microsoft and Azure Linux versions 3.0.

Impact

The impact specifics are not detailed in the provided data. Out-of-bounds reads can potentially lead to information disclosure or application instability, but no confirmed exploitation or impact severity is reported. No known exploits in the wild have been identified.

Summary

This vulnerability concerns the slip protocol's decode() function performing out-of-bounds reads against the compressed packet length in Microsoft and Azure Linux 3.0 products. The issue was cataloged by the Microsoft Security Response Center but lacks detailed technical disclosure or CVSS scoring. No exploit information or patch availability is currently documented.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 May 2026, 21:03 UTC

Technical details

References

Community reviews

Related threats