# CVE-2026-44589: nuxt-og-image SSRF — bypass of GHSA-pqhr-mp3f-hrpp / v6.2.5 fix (IPv6 + redirect)

> An incomplete IPv6 denylist and missing redirect validation in Nuxt OG Image allow attackers to bypass SSRF protections and access internal resources.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-c2rm-g55x-8hr5

## What is CVE-2026-44589?

CVE-2026-44589 is a low-severity server-side request forgery vulnerability in nuxt-modules og-image, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nuxt OG Image generates OG Images with Vue templates in Nuxt. The isBlockedUrl() denylist introduced in nuxt-og-image@6.2.5 to remediate GHSA-pqhr-mp3f-hrpp (Dmitry Prokhorov / Positive Technologies, March 2026) is incomplete. It has an incomplete IPv6 prefix list and is missing redirect re-validation. This vulnerability is fixed in 6.4.9.

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

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

2 open source packages ship an affected version, including nuxt-og-image.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nuxt-og-image` | npm | From 6.2.5 | 6.4.9 |
| `nuxt-og-image` | npm | From 6.2.5 | 6.4.9 |

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

Upgrade nuxt-og-image to 6.4.9 or later.

## Is CVE-2026-44589 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44589 is a low-severity server-side request forgery vulnerability in nuxt-modules og-image, published on 14 May 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-44589 in the wild and no public exploit code.

Affected packages and fixed versions:
- nuxt-og-image (npm): affected from 6.2.5; fixed in 6.4.9
- nuxt-og-image (npm): affected from 6.2.5; fixed in 6.4.9

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

## Sources

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

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