Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 31 March 2026.
- Which products and versions are affected?
- nuxt-og-image (npm) SEMVER:introduced=0,fixed=6.2.5; Nuxt Og-Image < 6.2.5.
- Is there a fix for This vulnerability?
- Yes. nuxt-og-image (npm): upgrade to 6.2.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run nuxt-og-image (npm) or Nuxt Og-Image at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- nuxt-og-image (npm): upgrade to 6.2.5 or later
npm install nuxt-og-image@6.2.5
Technical details
The vulnerability is a Server-Side Request Forgery (SSRF) in the /_og/d/ image generation endpoint. The endpoint accepts user-controlled parameters (style, html) without proper validation before passing them to the server-side renderer. Attackers can inject CSS background-image URLs, img src attributes, or SVG image hrefs pointing to internal addresses (127.0.0.1, private ranges, cloud metadata endpoints) to trigger server-side requests. No authentication or user interaction is required; the attack is triggered via simple GET requests. An attacker can scan internal services, read metadata credentials when verbose errors are enabled, and leak response content via base64-encoded error messages. The vulnerability is fixed in version 6.2.5 by blocking requests to private IP ranges, loopback addresses, link-local addresses, and cloud metadata endpoints, including protection against decimal/hexadecimal IP encoding bypasses.
Affected products
- Nuxt OG Image < 6.2.5
Timeline
- 2026-03-31: disclosed
- 2026-03-31: patched: Fixed in version 6.2.5