Vulnerabilities in pkg:npm/nuxt-og-image

PACKAGE
Advisory Identifier: GHSA-2x6f-rp82-ppmj
Advisory Summary

CVE-2026-102527 is a MODERATE nuxt og image cache poisoning vulnerability (CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data) affecting Nuxt og image libraries in the npm ecosystem. The issue involves nuxt og image cache poisoning through derivable cache keys on unsigned dynamic image routes. Remediation is available by upgrading affected packages to version 6.7.0.

6 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/nuxt-og-image

6 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/nuxt-og-image. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-2x6f-rp82-ppmj CVE-2026-102527 MODERATE Nuxt OG Image cache poisoning through derivable cache keys on unsigned dynamic image routes
GHSA-q8hw-4fvp-9rwv CVE-2026-61793 MODERATE Nuxt OG Image has unauthenticated SSRF via `fonts[].path` URL parameter
GHSA-c2rm-g55x-8hr5 CVE-2026-44589 LOW nuxt-og-image SSRF — bypass of GHSA-pqhr-mp3f-hrpp / v6.2.5 fix (IPv6 + redirect)
GHSA-mg36-wvcr-m75h CVE-2026-34405 MODERATE Nuxt OG Image is vulnerable to reflected XSS via query parameter injection into HTML attributes
GHSA-c7xp-q6q8-hg76 CVE-2026-34404 MODERATE Nuxt OG Image is vulnerable to Denial of Service via unbounded image dimensions
GHSA-pqhr-mp3f-hrpp - MODERATE Nuxt OG Image vulnerable to Server-Side Request Forgery via user-controlled parameters

CVE-2026-102527 at a Glance

CVE Identifier CVE-2026-102527
GHSA Identifier GHSA-2x6f-rp82-ppmj
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data
Affected Product Nuxt og image
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-102527

To remediate this vulnerability, upgrade all affected Nuxt og image dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nuxt-og-image fixed: 6.7.0
npm install nuxt-og-image@6.7.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls nuxt-og-image

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-102527, inspect your project dependencies using npm:

npm ls nuxt-og-image

Analyze the terminal output to locate any version of Nuxt og image in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.7.0), your application is affected.

Note: The npm ls nuxt-og-image command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data, where the product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted. In Nuxt og image, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

**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](https://github.com/nuxt-modules/og-image/security/advisories/GHSA-6c86-prf5-hj4h), 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_ ``` export function resolvePathCacheKey(e: H3Event, path: string, resolvedOptions?: Record<string, any>) { const siteConfig = getSiteConfig(e, { resolveRefs: true, }) const basePath = withoutTrailingSlash(withoutLeadingSlash(normalizeKey(path))) const hashParts: any[] = [ basePath, import.meta.prerender ? '' : siteConfig.url, ] // Hash resolved options (not raw query string) so unknown/extra query params // cannot produce unique cache keys and bypass the cache. if (resolvedOptions) hashParts.push(hash(resolvedOptions)) return [ (!basePath || basePath === '/') ? 'index' : basePath, hash(hashParts), ].join(':') } ``` In this case, `basePath` is obtained from the `_path` parameter, `resolvedOptions` are the normalized settings of the component, for example: _Listing 2. An example of `resolvedOptions`_ ``` {"emojis":"noto","extension":"png","width":1200,"height":600,"cacheMaxAgeSeconds":259200,"component":"OgImageDefaultImageTakumi"} ``` From the analysis of `resolvedOptions`, it was concluded that, in general, all parameters are known either from the direct link to the OG Image or from the server response. ## Vulnerability reproduction 1. Find the route to OG Image. _Figure 1. Demonstration of finding the route to OG Image_ <img width="974" height="361" alt="image" src="https://github.com/user-attachments/assets/d3ee6b54-d545-4a3b-8cbf-f82df99ed4d0" /> 2. Retrieve parameters from the server’s response, especially `cacheMaxAgeSeconds` (`cache-control` header, `s-maxage` key), the other parameters are known from the meta tags as well as from the `c_<component name>` parameter. _Figure 2. Obtaining parameters_ <img width="974" height="245" alt="image" src="https://github.com/user-attachments/assets/84a4cd8b-9281-47ef-b524-0047a0f6077a" /> 3. Generate a cache key using a script. _Listing 3. Srcipt_ ``` import {hash} from "ohash"; var url = "https://contoso.com" var obj = JSON.parse(`{"emojis":"noto","extension":"png","width":1200,"height":600,"cacheMaxAgeSeconds":259200,"component":"OgImageBlogPostTakumi"}`) var basePath = '/' var hashParts = [ basePath, url ] if (obj) hashParts.push(hash(obj)) console.log([ (!basePath || basePath === '/') ? 'index' : basePath, hash(hashParts), ].join(':')) ``` 4. Repeat the steps as in [the vulnerability 1](https://github.com/nuxt-modules/og-image/security/advisories/GHSA-6c86-prf5-hj4h), but transmit the obtained `cacheKey` in addition. 5. Thus, the same result as in [the vulnerability 1](https://github.com/nuxt-modules/og-image/security/advisories/GHSA-6c86-prf5-hj4h) was obtained. _Figure 4. Server response_ <img width="974" height="729" alt="image" src="https://github.com/user-attachments/assets/5895c0e8-e497-410d-bef9-f6f2f9649261" /> ## Credits Researcher: Dmitry Vanin (Positive Technologies)

CVE-2026-102527 Affected Nuxt og image Versions

1 component(s)
Fixed Versions:
6.7.0
Product / Package Ecosystem Affected Versions Fixed Version
nuxt-og-image
npm
≥ 6.2.5
< 6.7.0
6.7.0

References

Frequently Asked Questions

What is CVE-2026-102527?
CVE-2026-102527 is a security vulnerability in Nuxt og image involving Nuxt OG Image cache poisoning through derivable cache keys on unsigned dynamic image routes under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data.
Which Nuxt og image versions are affected?
Affected versions include releases prior to 6.7.0 across affected packages: nuxt-og-image.
What version fixes CVE-2026-102527?
Upgrading to 6.7.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nuxt-og-image affected?
Yes, nuxt-og-image is affected in releases prior to 6.7.0. Upgrade your dependency to 6.7.0 or later.
What CWE is associated with CVE-2026-102527?
CVE-2026-102527 is classified under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data (The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.).
How can I check npm dependencies for CVE-2026-102527?
Run the dependency tree command: 'npm ls nuxt-og-image'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2x6f-rp82-ppmj",
  "modified" : "2026-10-15T20:15:28Z",
  "published" : "2026-10-15T20:15:27Z",
  "aliases" : [ "CVE-2026-102527" ],
  "summary" : "Nuxt OG Image cache poisoning through derivable cache keys on unsigned dynamic image routes",
  "details" : "**Vendor:** Nuxt\n**Product:** Nuxt OG Image\n**Version:** 6.2.5\n**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. \n**Impact:** Content Spoofing\n**Vulnerable component:** route `/_og/d/*.png`\n**Exploitation conditions:** Access to the application\n**Mitigation:** Upgrade to 6.7.2 and set a sufficiently secure `secret` in config `ogImage`\n**Researcher:** Dmitry Vanin (Positive Technologies)\n\n## Research\nDuring [the previous vulnerability research](https://github.com/nuxt-modules/og-image/security/advisories/GHSA-6c86-prf5-hj4h), 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.\n\nHowever, the image is still generated from data transmitted to the attacker.\n\n_Listing 1. New code for generating indexes in cache_\n```\nexport function resolvePathCacheKey(e: H3Event, path: string, resolvedOptions?: Record<string, any>) {\n  const siteConfig = getSiteConfig(e, {\n    resolveRefs: true,\n  })\n  const basePath = withoutTrailingSlash(withoutLeadingSlash(normalizeKey(path)))\n  const hashParts: any[] = [\n    basePath,\n    import.meta.prerender ? '' : siteConfig.url,\n  ]\n  // Hash resolved options (not raw query string) so unknown/extra query params\n  // cannot produce unique cache keys and bypass the cache.\n  if (resolvedOptions)\n    hashParts.push(hash(resolvedOptions))\n  return [\n    (!basePath || basePath === '/') ? 'index' : basePath,\n    hash(hashParts),\n  ].join(':')\n}\n```\nIn this case, `basePath` is obtained from the `_path` parameter, `resolvedOptions` are the normalized settings of the component, for example:\n\n_Listing 2. An example of `resolvedOptions`_\n```\n{\"emojis\":\"noto\",\"extension\":\"png\",\"width\":1200,\"height\":600,\"cacheMaxAgeSeconds\":259200,\"component\":\"OgImageDefaultImageTakumi\"}\n```\nFrom the analysis of `resolvedOptions`, it was concluded that, in general, all parameters are known either from the direct link to the OG Image or from the server response.\n\n## Vulnerability reproduction\n\n1. Find the route to OG Image.\n_Figure 1. Demonstration of finding the route to OG Image_\n<img width=\"974\" height=\"361\" alt=\"image\" src=\"https://github.com/user-attachments/assets/d3ee6b54-d545-4a3b-8cbf-f82df99ed4d0\" />\n\n2. Retrieve parameters from the server’s response, especially `cacheMaxAgeSeconds` (`cache-control` header, `s-maxage` key), the other parameters are known from the meta tags as well as from the `c_<component name>` parameter.\n_Figure 2. Obtaining parameters_\n<img width=\"974\" height=\"245\" alt=\"image\" src=\"https://github.com/user-attachments/assets/84a4cd8b-9281-47ef-b524-0047a0f6077a\" />\n\n3. Generate a cache key using a script.\n_Listing 3. Srcipt_\n```\nimport {hash} from \"ohash\";\n\nvar url = \"https://contoso.com\"\n\nvar obj = JSON.parse(`{\"emojis\":\"noto\",\"extension\":\"png\",\"width\":1200,\"height\":600,\"cacheMaxAgeSeconds\":259200,\"component\":\"OgImageBlogPostTakumi\"}`)\n\nvar basePath = '/'\n\nvar hashParts = [\n    basePath,\n    url\n  ]\n  \nif (obj)\n\thashParts.push(hash(obj))\n\nconsole.log([\n    (!basePath || basePath === '/') ? 'index' : basePath,\n    hash(hashParts),\n  ].join(':'))\n```\n4. Repeat the steps as in [the vulnerability 1](https://github.com/nuxt-modules/og-image/security/advisories/GHSA-6c86-prf5-hj4h), but transmit the obtained `cacheKey` in addition.  \n5. Thus, the same result as in [the vulnerability 1](https://github.com/nuxt-modules/og-image/security/advisories/GHSA-6c86-prf5-hj4h) was obtained.\n_Figure 4. Server response_\n<img width=\"974\" height=\"729\" alt=\"image\" src=\"https://github.com/user-attachments/assets/5895c0e8-e497-410d-bef9-f6f2f9649261\" />\n\n## Credits\nResearcher: Dmitry Vanin (Positive Technologies)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nuxt-og-image"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.2.5"
      }, {
        "fixed" : "6.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nuxt-modules/og-image/security/advisories/GHSA-2x6f-rp82-ppmj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-102527"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nuxt-modules/og-image/pull/638"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nuxt-modules/og-image/commit/e6c5b53ce7f434ab8cbc91298dccfb2b515c56a5"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nuxt-modules/og-image"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nuxt-modules/og-image/releases/tag/v6.7.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-349" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-15T20:15:27Z",
    "nvd_published_at" : "2026-10-15T17:17:08Z"
  }
}