# CVE-2026-61704: link-preview-js DNS Rebinding SSRF Bypass / Incomplete Fix for CVE-2026-43897

> An attacker can bypass SSRF protections via DNS rebinding to access internal network resources using the link-preview-js library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-cpjf-6666-r8fx

## What is CVE-2026-61704?

CVE-2026-61704 is a high-severity server-side request forgery vulnerability in OP-Engineering link-preview-js, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Link Preview JS extracts web links information. Prior to 4.0.4, the resolveDNSHost mitigation in index.ts validates one resolved IP address but fetches the original hostname, allowing an attacker-controlled DNS server to return a public address during validation and a loopback or internal address during the final connection. This DNS rebinding condition bypasses the SSRF protection and can cause the server-side preview fetch to reach internal HTTP resources. Redirect handling is affected by the same validation-to-fetch mismatch. This issue is fixed in version 4.0.4.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-61704?

2 open source packages ship an affected version, including link-preview-js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `link-preview-js` | npm | All versions | 4.0.4 |
| `link-preview-js` | npm | All versions | 4.0.4 |

## How do I fix CVE-2026-61704?

Upgrade link-preview-js to 4.0.4 or later.

## Is CVE-2026-61704 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61704 and fix it if it is affected.

What it is: CVE-2026-61704 is a high-severity server-side request forgery vulnerability in OP-Engineering link-preview-js, published on 20 Aug 2026. 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-2026-61704 in the wild and no public exploit code.

Affected packages and fixed versions:
- link-preview-js (npm): affected all versions; fixed in 4.0.4
- link-preview-js (npm): affected all versions; fixed in 4.0.4

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-2026-61704/ (Markdown: https://insights.sbomify.com/CVE-2026-61704/index.md)
```

## Sources

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

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