How severe is CVE-2025-55177?

CVE-2025-55177 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-55177?

Affected package information for CVE-2025-55177 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-55177?

No fixed release is recorded for CVE-2025-55177 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2025-55177 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2025-55177 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2025-55177 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2025-55177, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-55177?

CVE-2025-55177 has an EPSS (Exploit Prediction Scoring System) score of 4.7%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-55177 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-55177 (Meta Platforms WhatsApp Incorrect Authorization Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-09-02. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-09-23. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-55177?

CVE-2025-55177 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-55177 published, and has it been updated?

CVE-2025-55177 was published on August 29, 2025 and was last updated on October 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

MEDIUM severity

CVE-2025-55177

MEDIUM

CVE-2025-55177 is a medium-severity (CVSS 5.4) CWE-863 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-09-02) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

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…

Published

Aug 29, 2025

Updated

Oct 7, 2026

Affected

2 products

Patched

See advisory

Exploits

1 known

Exploitation data as of Oct 21, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-09-02. Federal agencies were required to remediate by 2025-09-23.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-55177.

EPSS Exploitation Probability

via FIRST.org ↗

4.7%probability of exploitation in next 30 days

Lower Risk+0.43%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2025-55177 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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

Affected Products

2 products · 3 configurations

Application

whatsappwhatsapp

≥ 2.22.25.2 && < 2.25.21.78

range

Application

whatsapp businesswhatsapp

≥ 2.22.25.2 && < 2.25.21.78

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

danielw98/zero-click-exploit-analysis

CVE-2025-55177 + CVE-2025-43300: reverse-engineering the WhatsApp-ImageI

⭐ 5🍴 0Sep 2026

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2025-55177 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-55177 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N/E:F/RL:O/RC:C

CWE Classification

CWE-863CWE-863

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Aug 29, 2025

KEV added

Sep 2, 2025

Last updated

Oct 7, 2026

Identifiers

CVE-2025-55177

References

Webfacebook.com Webwhatsapp.com Webcisa.gov

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-863 are rated as high or higher (top: critical).

CVE-2026-77362CVE-2026-115883CVE-2026-115477CVE-2026-77366CVE-2026-77361GHSA-cxf3-9h37-7rr8GHSA-mhf7-xp6r-6qrcCVE-2026-73049Browse all CWE-863

Provenance

Sources

OSV.devNVDCISA KEVFIRST.org (EPSS)

Last verifiedOct 7, 2026