# CVE-2026-102527: Nuxt OG Image cache poisoning through derivable cache keys on unsigned dynamic image routes

> An attacker can poison the Open Graph image cache by manipulating unsigned dynamic routes, causing spoofed images to be served to users.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-2x6f-rp82-ppmj

## What is CVE-2026-102527?

CVE-2026-102527 is a medium-severity vulnerability in nuxt-modules og-image, published on 15 Oct 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. From 6.2.5 until 6.7.0, the dynamic /_og/d/*.png route accepts unsigned requests while resolvePathCacheKey() produces cache keys from the request path, site URL, and normalized rendering options exposed through image URLs and server responses. An unauthenticated attacker can provide attacker-controlled image data through the title parameter together with a derived cacheKey and populate the cache slot used for a legitimate Open Graph image, causing spoofed image content to be served to users. This issue is fixed in version 6.7.0.

Weakness: CWE-349 (Acceptance of Extraneous Untrusted Data With Trusted Data)

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

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.7.0 |
| `nuxt-og-image` | npm | From 6.2.5 | 6.7.0 |

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

Upgrade nuxt-og-image to 6.7.0 or later.

## Is CVE-2026-102527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102527 is a medium-severity vulnerability in nuxt-modules og-image, published on 15 Oct 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-102527 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.7.0
- nuxt-og-image (npm): affected from 6.2.5; fixed in 6.7.0

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

## Sources

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

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