LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32665: Verified groups not reliable

wire-ios is the iOS version of Wire, an open-source secure messaging app. wire-ios versions 3.8.0 and earlier have a bug in which a conversation could be incorrectly set to "unverified. This occurs when: - Self user is added to a new conversation - Self user is added to an existing conversation - All the participants in the conversation were previously marked as verified. The vulnerability is patched in wire-ios version 3.8.1. As a workaround, one can unverify & verify a device in the conversation.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Wire for iOS had a verification-state bug in versions 3.8.0 and earlier. In specific conversation membership situations, a conversation’s verified status could become unreliable. For organizations relying on Wire for sensitive communications, the priority is confirming iOS clients are upgraded to 3.8.1 or later.

Executive priority

Treat as high priority for teams using Wire as a trusted secure messaging channel. The business concern is not broad system compromise evidence, but loss of reliability in verification signals used to trust conversations.

Technical view

CVE-2021-32665 affects wire-ios <= 3.8.0 and is classified as CWE-345. The bug occurs when the self user is added to a new or existing conversation where all participants were previously verified. The vendor patched it in wire-ios 3.8.1; a workaround is to unverify and re-verify a device in the conversation.

Likely exposure

Exposure is limited to Wire iOS clients running version 3.8.0 or earlier. Risk is most relevant for users or organizations depending on Wire’s verified conversation/device trust indicators for sensitive communications.

Exploitation context

The source bundle does not cite active exploitation, and KEV status is false. The advisory describes conditions that can trigger incorrect verification behavior, but does not provide evidence of observed attacks.

Researcher notes

The available sources identify affected versions, trigger conditions, CWE-345 classification, CVSS 8.8, fixed version, and workaround. They do not establish active exploitation or provide broader platform impact beyond wire-ios.

Mitigation direction

  • Upgrade Wire iOS clients to version 3.8.1 or later.
  • If upgrade is delayed, use the vendor workaround: unverify and re-verify a device.
  • Prioritize users handling sensitive or regulated communications.
  • Review the Wire advisory for any newer vendor guidance.

Validation and detection

  • Inventory Wire iOS client versions and flag any <= 3.8.0.
  • Confirm upgraded devices report Wire iOS 3.8.1 or later.
  • Review affected conversations for unexpected verification-state changes.
  • Validate workaround completion where immediate upgrade was not possible.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-345: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32665 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-32665Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wireappwire-ios<= 3.8.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-345 · source CWE mapping

Insufficient Verification of Data Authenticity

Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.