Skip to main content
Mallory
UnratedVulnerability

CVE-2026-43671: Out-of-bounds write in SwiftNIO ByteBuffer via UInt32 truncation

Updated 5 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-43671CWE-190

SwiftNIO contains an out-of-bounds memory corruption vulnerability in ByteBuffer index and length handling. According to the provided advisory, affected helper functions perform unsafe UInt32(truncatingIfNeeded:) conversions on attacker-influenced index, offset, or length values. When values larger than UInt32.max are supplied, truncation can wrap the value and cause incorrect buffer position or size calculations, leading to out-of-bounds writes or reads and corruption of buffer contents or outbound packets.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may result in out-of-bounds memory writes or reads, heap memory corruption, deterministic process crashes, and logical corruption of ByteBuffer contents or generated outbound packets. Depending on application behavior and memory layout, this can cause denial of service and potentially more severe memory-safety consequences.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, validate all index, offset, and length values passed to affected ByteBuffer methods and reject any value greater than UInt32.max (4,294,967,295). Applications that compute buffer positions from untrusted input or process very large payloads should add explicit bounds checks before invoking ByteBuffer operations.

Remediation

Patch, then assume compromise.

Upgrade swift-nio to version 2.100.0 or later. The provided advisory states that the fix replaces unsafe UInt32(truncatingIfNeeded:) conversions with overflow-trapping UInt32(_) conversions in the affected helper functions, preventing silent truncation of oversized values.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-43671 exploited in the wild?
As of Jun 14, 2026, Mallory has no reports of CVE-2026-43671 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-43671?
As of Jun 14, 2026, Mallory has found no public exploit for CVE-2026-43671.
Is there a patch for CVE-2026-43671?
Upgrade swift-nio to version 2.100.0 or later. The provided advisory states that the fix replaces unsafe UInt32(truncatingIfNeeded:) conversions with overflow-trapping UInt32(_) conversions in the affected helper functions, preventing silent truncation of oversized values.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.