CVE-2026-35049
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedwire-ios is an iOS client for the Wire secure messaging application. Prior to version 4.16.0, upon receiving a crafted malicious Proteus external message with an encrypted payload that is shorter than 16 bytes, the Wire iOS client crashes. The crash is triggered automatically after message receival with no user interaction. Since the malicious message persists in the conversation, the app enters a crash loop on relaunch and cannot be reopened until the local state is wiped. This issue has been fixed with version 4.16.0 which introduces the missing length check and is available via the App Store. No known workarounds are available.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA missing length check in the Wire iOS client's Proteus message handling causes a crash when processing encrypted payloads shorter than 16 bytes. The vulnerability is triggered automatically upon receipt of a malicious message, and due to message persistence in the conversation, the app enters an unrecoverable crash loop requiring local state wipe.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Wire iOS versionOpen the App Store app, tap your profile, go to Purchased or Apps, find Wire, and note the version number. Alternatively, open the Wire app, go to Settings, scroll to About, and record the version shown.Affected if The installed version is earlier than 4.16.0 (for example, 4.15.x, 4.14.x, or earlier)
-
Verify message reception is activeConfirm the Wire iOS client is configured to receive messages from external contacts or federated servers. This is the default state for most users.Affected if The app is connected to a server and can receive incoming Proteus encrypted messages from external senders
-
Confirm crash behavior patternAfter receiving any external message, observe whether the app crashes immediately or enters a persistent crash loop when the conversation is opened on relaunch. The crash is triggered specifically by malformed encrypted payloads shorter than 16 bytes.Affected if The app exhibits repeated crashes when opening specific conversations after receiving external messages, and the crash persists across app restarts
If the installed Wire iOS version is below 4.16.0 and the device can receive external Proteus messages, it is vulnerable to this buffer under-read crash.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Wire iOS version 4.16.0 or later, which implements the missing payload length validation. No workarounds exist; the only recovery method for affected versions is wiping local application state.
4.16.0
- Update the Wire iOS application to version 4.16.0 or later through the App Store
- If the app is currently in a crash loop due to the malicious message, clear the app's local data/state after updating to version 4.16.0 to exit the crash loop
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35049 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data