<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 19 Oct 2026 17:54:43 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-102527</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-102527</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-102527</guid>
    </item>
    <item>
      <title>GHSA-2x6f-rp82-ppmj — Nuxt OG Image cache poisoning through derivable cache keys on unsigned dynamic image routes</title>
      <link>https://db.gcve.eu/vuln/ghsa-2x6f-rp82-ppmj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt-og-image&lt;/p&gt;
&lt;p&gt;**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)&lt;/p&gt;
&lt;p&gt;## 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.&lt;/p&gt;
&lt;p&gt;However, the image is still generated from data transmitted to the attacker.&lt;/p&gt;
&lt;p&gt;_Listing 1. New code for generating indexes in cache_
```
export function resolvePathCacheKey(e: H3Event, path: string, resolvedOptions?: Record&amp;lt;string, any&amp;gt;) {
  const siteConfig = getSiteConfig(e, {
    resolveRefs: true,
  })
  const basePath = withoutTrailingSlash(withoutLeadingSlash(normalizeKey(path)))
  const hashParts: any[] = [
    basePath,
    import.meta.prerender ? &amp;#39;&amp;#39; : siteConfig.url,
  ]
  // Hash resolved options (not raw query string) so unknown/extra query params
  // cannot produce unique cache keys…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nuxt-og-image&lt;/p&gt;
&lt;p&gt;**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)&lt;/p&gt;
&lt;p&gt;## 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.&lt;/p&gt;
&lt;p&gt;However, the image is still generated from data transmitted to the attacker.&lt;/p&gt;
&lt;p&gt;_Listing 1. New code for generating indexes in cache_
```
export function resolvePathCacheKey(e: H3Event, path: string, resolvedOptions?: Record&amp;lt;string, any&amp;gt;) {
  const siteConfig = getSiteConfig(e, {
    resolveRefs: true,
  })
  const basePath = withoutTrailingSlash(withoutLeadingSlash(normalizeKey(path)))
  const hashParts: any[] = [
    basePath,
    import.meta.prerender ? &amp;#39;&amp;#39; : siteConfig.url,
  ]
  // Hash resolved options (not raw query string) so unknown/extra query params
  // cannot produce unique cache keys…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-2x6f-rp82-ppmj</guid>
    </item>
  </channel>
</rss>
