Vulnerability in nuxt-og-image (CVE-2026-102527)
Summary
Vulnerability in nuxt-og-image (CVE-2026-102527). Risk of unauthorized operations or information disclosure. Exploitable via title. Mitigation: upgrade to 6.7.0 or later.
Original description
The description as published by the source.
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
export function resolvePathCacheKey(e: H3Event, path: string, resolvedOptions?: Record) {
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…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-102527 has been found in nuxt-og-image.
Attackers can target a specific entry point like title over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nuxt-og-image to 6.7.0 or later.
If unsure, ask your IT team or search "nuxt-og-image CVE-2026-102527" on the vendor's site.
CVE-2026-102527 (nuxt-og-image) — CWE-349
Attack surface: title / secret / ogImage / basePath
Patched: 6.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-349) exists in nuxt-og-image. Attackers reach the vulnerable code path via title.
Check the vendor advisory for the affected versions of nuxt-og-image. Attack surface: title / secret / ogImage / basePath.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.7.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nuxt-og-image' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nuxt-og-image' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nuxt-og-imageを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade nuxt-og-image to 6.7.0ステージング環境で 6.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com