IDORSSRFAUTH BYPASSJWT FORGERYRACE CONDITIONXXEBROKEN OBJECT-LEVEL AUTHPRIVILEGE ESCALATIONMASS ASSIGNMENTGRAPHQL INTROSPECTION ABUSEIDORSSRFAUTH BYPASSJWT FORGERYRACE CONDITIONXXEBROKEN OBJECT-LEVEL AUTHPRIVILEGE ESCALATIONMASS ASSIGNMENTGRAPHQL INTROSPECTION ABUSE
Impactr Logoimpactr
FeaturesHow it worksEvidencePricingLearnVulnerability DBCompare
  1. Home
  2. Vulnerability Database
  3. CVE-2025-55177
CVE-2025-55177 CISA KEV — actively exploited

Meta Platforms WhatsApp Incorrect Authorization Vulnerability

Facebook — WhatsApp Desktop for Mac

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.

CVSS scoreMedium

5.4

EPSS — exploitation probabilityLow

4.1%

Vector breakdown

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Published
Aug 29, 2025
Modified
Feb 26, 2026
Added to KEV
Sep 2, 2025
Federal patch due
Sep 23, 2025

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Proof-of-concept & exploitation references

Weaponization

Nuclei template

Not found

Metasploit module

Not found

Public repositories whose name or description references CVE-2025-55177, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.

No public GitHub repositories referencing CVE-2025-55177 were found at last check. Absence here is not proof no exploit exists - see the references below for vendor advisories and write-ups.

References

  • facebook.com
  • whatsapp.com

Frequently asked questions

What is CVE-2025-55177?

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.

How severe is CVE-2025-55177?

CVE-2025-55177 has a CVSS base score of 5.4 out of 10 (CVSS 3.1).

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

Yes. CVE-2025-55177 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Sep 2, 2025, meaning CISA has confirmed evidence of active exploitation.

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

4.1% - meaning FIRST.org's EPSS model estimates a 4.1% probability this vulnerability will be exploited in the wild within 30 days (90% percentile among all scored CVEs).

Cross-checked against

  • NVD (NIST)
  • MITRE CVE Record
  • CISA KEV
  • FIRST.org EPSS
  • GitHub Advisory Database
  • GitHub public repository search

Impactr finds and proves whether CVE-2025-55177 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.

Join the waitlist
← Vulnerability database
Impactr Logoimpactr

Built by hackers, for the code you ship. Autonomous AI penetration testing for modern web apps and APIs.

© 2026 Impactr

Product

FeaturesCoverageUse casesEvidencePricingWaitlist

Resources

VulnerabilitiesVulnerability databaseGuidesComparisonsGlossaryCWE databaseBy industryBy languageHTTP status codesSecurity headers

Company

ContactTwitterLinkedInGitHub