# CVE-2025-56139: Other in n/a

> Attackers can deceive users by displaying trusted link previews for malicious URLs in LinkedIn Android posts, facilitating phishing attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-pf9x-3p57-vp26

## What is CVE-2025-56139?

CVE-2025-56139 is a medium-severity vulnerability in n/a, published on 3 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LinkedIn Mobile Application for Android version 4.1.1087.2 fails to update link preview metadata (image, title, description) when a user replaces the original URL in a post or comment before publishing. As a result, the stale preview remains visible while the clickable link points to a different URL, which can be malicious. This UI misrepresentation enables attackers to deceive users by displaying trusted previews for harmful links, facilitating phishing attacks and user confusion.

Weakness: CWE-449 (The UI Performs the Wrong Action)

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

It affects 1 product.


Products: Linkedin Linkedin.

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

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

## Is CVE-2025-56139 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56139 is a medium-severity vulnerability in n/a, published on 3 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-56139 in the wild and no public exploit code.

Affected product: n/a. 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-56139/ (Markdown: https://insights.sbomify.com/CVE-2025-56139/index.md)
```

## Sources

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

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