Security Resilience

CVE-2025-55177

Access Control in Whatsapp 2.22.25.2 – 2.25.21.73

CISA KEVActive ExploitationEUVD ExploitedAccess Control
Published
29 August 2025
Modified
18 October 2026
KEV Added
02 September 2025
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.13 96th percentile
Risk Priority 75 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-55177 is a medium-severity Incorrect Authorization (CWE-863) vulnerability in Whatsapp. Its CVSS base score is 5.4 (Medium).

Operationally, ranked in the top 4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-55177 is an incomplete authorization vulnerability (CWE-863) in the handling of linked device synchronization messages within WhatsApp for iOS versions prior to v2.25.21.73, WhatsApp Business for iOS prior to v2.25.21.78, and WhatsApp for Mac prior to v2.25.21.78. This flaw enables an unrelated user to trigger the processing of content from an arbitrary URL on a target's device. The vulnerability carries a CVSS v3.1 base score of 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N), indicating medium severity with network accessibility, low attack complexity, and requirements for low privileges.

An attacker with low privileges, such as an unrelated WhatsApp user, can exploit this issue over the network without user interaction to force the target's device to process malicious content from a remote URL. While standalone exploitation yields limited confidentiality and integrity impacts, the vulnerability's description notes that, when chained with an Apple OS-level flaw (CVE-2025-43300), it may enable sophisticated attacks targeting specific users.

Advisories from Meta's Facebook security page (https://www.facebook.com/security/advisories/cve-2025-55177), WhatsApp's 2025 security advisories (https://www.whatsapp.com/security/advisories/2025/), and CISA's Known Exploited Vulnerabilities catalog (https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-55177) recommend updating to the patched versions (WhatsApp for iOS v2.25.21.73 or later, WhatsApp Business for iOS v2.25.21.78 or later, and WhatsApp for Mac v2.25.21.78 or later) as the primary mitigation.

This issue has been added to CISA's Known Exploited Vulnerabilities catalog, signaling active exploitation concerns, particularly in targeted attacks when combined with CVE-2025-43300.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Incomplete authorization of linked device synchronization messages in WhatsApp for iOS prior to v2.25.21.73, WhatsApp Business for iOS v2.25.21.78, and WhatsApp for Mac v2.25.21.78 could have allowed an unrelated user to trigger processing of content from an arbitrary URL on…

more

a target’s device. We assess that this vulnerability, in combination with an OS-level vulnerability on Apple platforms (CVE-2025-43300), may have been exploited in a sophisticated attack against specific targeted users.

CWE(s)
KEV Date Added
02 September 2025

Related Threats

CVEs Like This One

CVE-2019-3568Same product: Whatsapp Whatsappboth on KEV
CVE-2025-55179Same product: Whatsapp Whatsapp
CVE-2019-18426Same product: Whatsapp Whatsappboth on KEV
CVE-2025-30401Same product: Whatsapp Whatsapp
CVE-2023-38537Same product: Whatsapp Whatsapp
CVE-2026-23863Same product: Whatsapp Whatsapp
CVE-2023-38538Same product: Whatsapp Whatsapp
CVE-2026-42016Shared CWE-863both on KEV
CVE-2023-24880Shared CWE-863both on KEV
CVE-2024-38856Shared CWE-863both on KEV

Affected Assets

whatsapp
whatsapp
2.22.25.2 — 2.25.21.73 · 2.22.25.2 — 2.25.21.78
whatsapp
whatsapp business
2.22.25.2 — 2.25.21.78

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 directly requires correct enforcement of authorization decisions on every access request, structurally preventing incorrect checks.

AC-24 ensures access-control decisions are made and applied consistently, reducing the chance of an incorrect authorization result.

A reference monitor that is always invoked and tamper-proof forces every authorization decision through a verified, correct path.

Least-privilege assignments shrink the set of authorizations that must be checked correctly, limiting exposure to flawed checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.18's provisioning, revocation, review and adjustment of access rights (incl. before role changes/termination, with segregation and owner approval) directly stops incorrect authorization decisions from being exploitable in the vast majority of cases; the bounded remainder is incorrectness inside the authorization logic itself (e.g. flawed conditional or missing check) rather than rights that were wrongly granted.

blocks

A.8.3 directly mandates restricting access to information per policies via configuration, identity/group controls, isolation, and dynamic techniques that enforce correct authorization decisions, addressing most but not all slices of CWE-863 (e.g., remainder in non-access-decision authorization errors like timing or environmental factors).

blocks

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-863, a class-level weakness, and none of its children carries one either.

References