CVE-2026-61704

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

August 20, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated Aug 20, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

Release 4.0.4

Patch available: OP-Engineering/link-preview-js 4.0.4

https://github.com/OP-Engineering/link-preview-js/releases/tag/4.0.4
github_commit Patch Available

commit f3a3dd84adbb (OP-Engineering/link-preview-js)

Patch available: OP-Engineering/link-preview-js 4.0.4 (contains commit f3a3dd84adbb)

https://github.com/OP-Engineering/link-preview-js/commit/f3a3dd84adbb9d32d06a933f44ff3eaa837f9a12
github_commit Patch Available

commit 6ee25043dd60 (OP-Engineering/link-preview-js)

Patch available: OP-Engineering/link-preview-js 4.0.4 (contains commit 6ee25043dd60)

https://github.com/OP-Engineering/link-preview-js/commit/6ee25043dd60b097eb70b4ce049aac94b28239e3
github_pr Patch Available

fix: harden SSRF protection against DNS rebinding

Patch available: OP-Engineering/link-preview-js 4.0.4 (PR #181 merged 2026-06-23)

https://github.com/OP-Engineering/link-preview-js/pull/181
github Patch Available🟡 PoC Available

link-preview-js 4.0.3 DNS Rebinding SSRF Bypass / Incomplete Fix for CVE-2026-43897 · Advisory · OP-Engineering/link-preview-js · GitHub

https://github.com/OP-Engineering/link-preview-js/security/advisories/GHSA-cpjf-6666-r8fx

Vendor Advisories for CVE-2026-61704(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
link-preview-js—4.0.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 21:19 UTCEG score recompute
  2. 2026-09-18 20:20 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 21:23 UTCEG score recompute
  5. 2026-09-16 20:02 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 07:04 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 05:46 UTCEG score recompute
  10. 2026-09-14 04:51 UTCEG score recompute
  11. 2026-09-12 16:05 UTCEG score recompute
  12. 2026-09-11 15:33 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 09:37 UTCEPSS rescore
  15. 2026-09-10 15:01 UTCEG score recompute
  16. 2026-09-09 01:58 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 03:49 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-07 01:00 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-06 00:23 UTCEG score recompute
  23. 2026-09-04 23:51 UTCEG score recompute
  24. 2026-09-04 11:10 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescore
Show 27 more
  1. 2026-09-02 22:22 UTCEG score recompute
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 21:48 UTCEG score recompute
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 09:33 UTCEG score recompute
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-30 20:36 UTCEG score recompute
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 08:21 UTCEG score recompute
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-29 07:45 UTCEG score recompute
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-27 18:34 UTCEG score recompute
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 16:14 UTCEG score recompute
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 15:23 UTCEG score recompute
  18. 2026-08-25 15:16 UTCEG score recompute
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-24 19:38 UTCEG score recompute
  21. 2026-08-23 06:51 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 06:20 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 17:33 UTCEG score recompute
  26. 2026-08-20 16:33 UTCEG score recompute
  27. 2026-08-20 16:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61704?
CVE-2026-61704 is a high vulnerability published on August 20, 2026. 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…
When was CVE-2026-61704 disclosed?
CVE-2026-61704 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61704 actively exploited?
CVE-2026-61704 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.6% of all scored CVEs.
What is the CVSS score of CVE-2026-61704?
CVE-2026-61704 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-61704?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61704, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61704

Explore →

Is Your Infrastructure Affected by CVE-2026-61704?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs