Vulnerability in nuxt-og-image (CVE-2026-61793)
Summary
Vulnerability in nuxt-og-image (CVE-2026-61793). Risk of unauthorized operations or information disclosure. Exploitable via JSON.parse. Mitigation: upgrade to 6.7.0 or later.
Original description
The description as published by the source.
Summary
nuxt-og-image exposes an unauthenticated HTTP endpoint at /_og/d/** that base64url-decodes and JSON.parses a fonts URL segment, then passes each fonts[i].path value directly into fetch() server-side without any URL validation (no scheme allowlist, no loopback/RFC1918 block, no host allowlist, no DNS rebinding mitigation).
Under the module's documented default configuration (security.strict = false, security.secret = "", restrictRuntimeImagesToOrigin = false), any caller able to reach the deployed Nuxt site can force the Nuxt server to issue arbitrary outbound GET requests to any host reachable from the server - including loopback, RFC1918 LAN, and cloud metadata services (AWS IMDS, GCE/Azure metadata, Kubernetes kubelet, internal admin panels, Redis/etcd/Consul/Vault HTTP APIs).
The chain is blind (Satori consumes the response as font bytes and silently discards non-fonts) but a robust side-channel exists: the outer HTTP status is 500 when the SSRF target returns 2xx, and 200 when it fails or returns non-2xx. This is sufficient to (a) enumerate live internal services and open ports, (b) confirm IMDSv1 reachability, and (c) detect credential issuance on environments still allowing IMDSv1.
Demonstrated end-to-end on a stock npm create nuxt@latest install with the module's documented default usage.
Detail
Endpoint registration (unauthenticated)
The module registers /_og/d/** and /_og/s/** with no auth…
Source: NIST National Vulnerability Database 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-61793 has been found in nuxt-og-image.
Attackers can target a specific entry point like JSON.parse 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-61793" on the vendor's site.
CVE-2026-61793 (nuxt-og-image) — CWE-20
Attack surface: JSON.parse / fonts / GET / kubelet
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-20) exists in nuxt-og-image. Attackers reach the vulnerable code path via JSON.parse.
Check the vendor advisory for the affected versions of nuxt-og-image. Attack surface: JSON.parse / fonts / GET / kubelet.
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
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com