Skip to content

← Actionable
Medium, CVSS 6.9amended

Nuxt OG Image cache poisoning through derivable cache keys on unsigned dynamic image routes

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nuxt-og-image 6.7.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-102527: 0.19% estimated exploitation activity in the next 30 days; percentile 8.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Vendor: Nuxt Product: Nuxt OG Image Version: 6.2.5 Description: Due to the specifics of caching and key generation in the Open Graph image cache created by the module, an unauthenticated attacker can modify the content of the image (for example, the title parameter) that is delivered to the user. Impact: Content Spoofing Vulnerable component: route /og/d/.png Exploitation conditions: Access to the application Mitigation: Upgrade to 6.7.2 and set a sufficiently secure secret in config ogImage Researcher: Dmitry Vanin (Positive Technologies) Research During the previous vulnerability research, it was discovered that version 6.2.5 changed the mechanism for generating cache indexes; it now takes into account the parameters passed during image generation. However, the image is still generated from data transmitted to the attacker. Listing 1. New code for generating indexes in cache In this case, basePath is obtained from the path parameter, resolvedOptions are the normalized settings of…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-2x6f-rp82-ppmj

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-2x6f-rp82-ppmj

  4. Revision 1 · created ·

    Published from ghsa record GHSA-2x6f-rp82-ppmj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-102527

Advisory: Nuxt OG Image cache poisoning through derivable cache keys on unsigned dynamic image routes
IDs: CVE-2026-102527, GHSA-2x6f-rp82-ppmj
Record: https://patchnext.com/advisories/cve-2026-102527 (revision 4, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nuxt-og-image 6.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nuxt-og-image: affected >= 6.2.5, < 6.7.0; fixed in 6.7.0

## Suggested inspection (read-only)
- `npm ls nuxt-og-image --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nuxt-og-image.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2x6f-rp82-ppmj (GitHub-reviewed advisory GHSA-2x6f-rp82-ppmj lists affected ranges: npm nuxt-og-image >=6.2.5 <6.7.0)
- Verified: https://osv.dev/vulnerability/GHSA-2x6f-rp82-ppmj (OSV record GHSA-2x6f-rp82-ppmj lists affected ranges: npm nuxt-og-image >=6.2.5 <6.7.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…