Is CVE-2026-102527 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-102527 being exploited in the wild.

How severe is CVE-2026-102527?

Medium severity, with a CVSS score of 4, published 15 October 2026.

Which products and versions are affected?

nuxt-og-image (npm) >= 6.2.5, < 6.7.0, SEMVER:introduced=6.2.5,fixed=6.7.0; Nuxt Og-Image before 6.7.2.

How is CVE-2026-102527 attacked?

It is attacked over the network.

Am I affected by CVE-2026-102527?

Check whether you run nuxt-og-image (npm) or Nuxt Og-Image at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102527: Nuxt OG Image cache poisoning through derivable cache keys

Q: Is there a fix for CVE-2026-102527?

Yes. nuxt-og-image (npm): upgrade to 6.7.0 or later. Until then: Upgrade to version 6.7.2 and configure a sufficiently secure `secret` in the `ogImage` configuration to prevent cache key derivation. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-102527 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-102527?

Check whether you run nuxt-og-image (npm) or Nuxt Og-Image at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-102527 · Severity: medium · CVSS 4 · Published 2026-10-15

Nuxt OG Image is a module that generates Open Graph preview images for web applications. An attacker can forge cache keys to poison the image cache and deliver malicious content—such as altered titles or images—to users without authentication, enabling content spoofing attacks.

Technologies: nuxt-og-image (npm), Nuxt Og-Image. Vendors: npm, Nuxt.

Quick answers

Is CVE-2026-102527 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-102527 being exploited in the wild.
How severe is CVE-2026-102527?: Medium severity, with a CVSS score of 4, published 15 October 2026.
Which products and versions are affected?: nuxt-og-image (npm) >= 6.2.5, < 6.7.0, SEMVER:introduced=6.2.5,fixed=6.7.0; Nuxt Og-Image before 6.7.2.
Is there a fix for CVE-2026-102527?: Yes. nuxt-og-image (npm): upgrade to 6.7.0 or later. Until then: Upgrade to version 6.7.2 and configure a sufficiently secure `secret` in the `ogImage` configuration to prevent cache key derivation. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-102527 attacked?: It is attacked over the network.
Am I affected by CVE-2026-102527?: Check whether you run nuxt-og-image (npm) or Nuxt Og-Image at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

nuxt-og-image (npm): upgrade to 6.7.0 or later
```
npm install nuxt-og-image@6.7.0
```

Upgrade to version 6.7.2 and configure a sufficiently secure `secret` in the `ogImage` configuration to prevent cache key derivation.

Technical details

The vulnerability exists in the cache key generation mechanism for the `/_og/d/*.png` route, which incorporates parameters that are either publicly known (from HTTP headers, meta tags, and URL parameters) or easily derived. An unauthenticated attacker can reconstruct the cache key and inject malicious image content that persists for the cache duration. The issue affects versions before 6.7.2 when the ogImage secret is not sufficiently secure.

Affected products

Nuxt OG Image before 6.7.2

Identifiers

CVE-2026-102527
GHSA-2x6f-rp82-ppmj

Timeline

2026-10-15: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.