Approved changes feed: RSS · Atom
cpe:2.3:a:wireapp:wire-ios:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Wireapp (d04fd6f7-6e70-5472-9b75-3c59ffc0e9a7) |
|---|---|
| Product | Wire Ios (1b9d5e5c-8977-58cd-9661-9b39a2cb8d1e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-35049 |
vulnerable | 2026-06-08 07:59:13.444439 |
wire-ios has Persistent Remote DoS via Integer Underflow
MEDIUM (6.5)
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.
Published: 2026-06-02T18:35:48.536Z
Updated: 2026-06-03T13:55:29.998Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-49846 |
vulnerable | 2026-06-08 07:29:15.001250 |
wire-ios accidentally logs message contents
wire-ios is an iOS client for the Wire secure messaging application. From Wire iOS 3.111.1 to before 3.124.1, messages that were visible in the view port have been logged to the iOS system logs in clear text. Wire application logs created and managed by the application itself were not affected, especially not the logs users can export and send to Wire support. The iOS logs can only be accessed if someone had (physical) access to the underlying unlocked device. The issue manifested itself by calling canOpenUrl() and passing an invalid URL object. When iOS then performs the check and fails, it logs the contents to the system log. This is not documented behaviour. Wire released an emergency fix with version 3.124.1. As a workaround, users can reset their iOS device to remove the offending logs. Since Wire cannot access or modify iOS system logs, there's no other workaround other than a reset.
Published: 2025-07-03T16:41:34.228Z
Updated: 2025-07-03T19:23:39.700Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31009 |
vulnerable | 2026-06-08 05:43:39.969927 |
DoS vulnerability: Invalid Accent Colors
MEDIUM (5.7)
wire-ios is an iOS client for the Wire secure messaging application. Invalid accent colors of Wire communication partners may render the iOS Wire Client partially unusable by causing it to crash multiple times on launch. These invalid accent colors can be used by and sent between Wire users. The root cause was an unnecessary assert statement when converting an integer value into the corresponding enum value, causing an exception instead of a fallback to a default value. This issue is fixed in [wire-ios](https://github.com/wireapp/wire-ios/commit/caa0e27dbe51f9edfda8c7a9f017d93b8cfddefb) and in Wire for iOS 3.100. There is no workaround available, but users may use other Wire clients (such as the [web app](https://app.wire.com)) to continue using Wire, or upgrade their client.
Published: 2022-06-23T06:40:10.000Z
Updated: 2025-04-23T18:09:07.862Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23625 |
vulnerable | 2026-06-08 05:40:58.063519 |
DoS vulnerability: Malformed Resource Identifiers
MEDIUM (6.5)
Wire-ios is a messaging application using the wire protocol on apple's ios platform. In versions prior to 3.95 malformed resource identifiers may render the iOS Wire Client completely unusable by causing it to repeatedly crash on launch. These malformed resource identifiers can be generated and sent between Wire users. The root cause lies in [wireapp/wire-ios-transport](https://github.com/wireapp/wire-ios-transport), where code responsible for removing sensible tokens before logging may fail and lead to a crash (Swift exception) of the application. This causes undesirable behavior, however the (greater) Wire system is still functional. Users are advised to upgrade as soon as possible. There are no known workarounds for this issue.
Published: 2022-03-11T18:00:15.000Z
Updated: 2025-04-23T18:54:35.233Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-41094 |
vulnerable | 2026-06-08 05:35:19.723531 |
Mandatory encryption at rest can be bypassed (UI) in Wire app
MEDIUM (4.2)
Wire is an open source secure messenger. Users of Wire by Bund may bypass the mandatory encryption at rest feature by simply disabling their device passcode. Upon launching, the app will attempt to enable encryption at rest by generating encryption keys via the Secure Enclave, however it will fail silently if no device passcode is set. The user has no indication that encryption at rest is not active since the feature is hidden to them. This issue has been resolved in version 3.70
Published: 2021-10-04T18:20:13.000Z
Updated: 2024-08-04T02:59:31.399Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-41093 |
vulnerable | 2026-06-08 05:35:19.722339 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32666 |
vulnerable | 2026-06-08 05:32:07.796990 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32665 |
vulnerable | 2026-06-08 05:32:07.795626 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21301 |
vulnerable | 2026-06-08 05:29:11.579009 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.