# CVE-2026-35049: wire-ios has Persistent Remote DoS via Integer Underflow

> Attackers can cause a persistent denial of service in the Wire iOS app by sending a short encrypted message, crashing the client until local data is wiped.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-v6wg-c7qc-x66g

## What is CVE-2026-35049?

CVE-2026-35049 is a medium-severity vulnerability in wireapp wire-ios, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

wire-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.

Weakness: CWE-20 (Improper Input Validation), CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2026-35049?


## How do I fix CVE-2026-35049?

No fix has been published for CVE-2026-35049 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35049 being exploited?

There is no known exploitation of CVE-2026-35049 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35049 and fix it if it is affected.

What it is: CVE-2026-35049 is a medium-severity vulnerability in wireapp wire-ios, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35049 in the wild and no public exploit code.

Affected product: wireapp wire-ios. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35049/ (Markdown: https://insights.sbomify.com/CVE-2026-35049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35049
- OSV: https://osv.dev/vulnerability/CVE-2026-35049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35049/
Summaries are generated and may contain mistakes; the official description above is the record.