# CVE-2025-55179: Server-side request forgery in WhatsApp Business for iOS

> Incomplete validation in WhatsApp allows triggering media processing from arbitrary URLs, potentially exposing internal network resources or data.

- **Severity:** Medium 5.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2025
- **Updated:** 18 Nov 2025
- **Also known as:** GHSA-qfr3-q6jf-3gx8

## What is CVE-2025-55179?

CVE-2025-55179 is a medium-severity server-side request forgery vulnerability in Facebook WhatsApp Business for iOS, published on 18 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incomplete validation of rich response messages in WhatsApp for iOS prior to v2.25.23.73, WhatsApp Business for iOS v2.25.23.82, and WhatsApp for Mac v2.25.23.83 could have allowed a user to trigger processing of media content from an arbitrary URL on another user’s device. We have not seen evidence of exploitation in the wild.

## Which versions are affected by CVE-2025-55179?

It affects 2 products.


Products: Whatsapp Whatsapp, Whatsapp Whatsapp Business.

## How do I fix CVE-2025-55179?

No fix has been published for CVE-2025-55179 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-55179 being exploited?

There is no known exploitation of CVE-2025-55179 in the wild and no public exploit code.

## Other vulnerabilities in Facebook WhatsApp Business for iOS

- [CVE-2019-3568](https://insights.sbomify.com/CVE-2019-3568/): WhatsApp VOIP Stack Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2019-18426](https://insights.sbomify.com/CVE-2019-18426/): WhatsApp Cross-Site Scripting (high 8.2, exploited in the wild)
- [CVE-2025-55177](https://insights.sbomify.com/CVE-2025-55177/): Meta Platforms WhatsApp Incorrect Authorization (medium 5.4, exploited in the wild)
- [CVE-2022-36934](https://insights.sbomify.com/CVE-2022-36934/): Integer overflow in WhatsApp Business for Android (critical 9.8)
- [CVE-2021-24042](https://insights.sbomify.com/CVE-2021-24042/): Memory corruption in WhatsApp Business for Android (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55179 and fix it if it is affected.

What it is: CVE-2025-55179 is a medium-severity server-side request forgery vulnerability in Facebook WhatsApp Business for iOS, published on 18 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55179 in the wild and no public exploit code.

Affected product: Facebook WhatsApp Business for iOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55179/ (Markdown: https://insights.sbomify.com/CVE-2025-55179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55179
- OSV: https://osv.dev/vulnerability/CVE-2025-55179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55179/
Summaries are generated and may contain mistakes; the official description above is the record.