How to Fix CVE-2026-34404: Nuxt OG Image vulnerable to DoS via image generation in og-image
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-5740: Command Injection in Mattermost — Command Injection in Mattermost
- How to Fix CVE-2026-40933: OS command injection in Flowise — OS command injection in Flowise
- How to Fix CVE-2026-0898: Access Control Bypass in Pega Robot Studio , Access Control Bypass in Pega Robot Studio
- How to Fix CVE-2026-25374: Critical Vulnerability in Spa and Salon , Critical Vulnerability in Spa and Salon
- How to Fix CVE-2026-32899: Access Control Bypass in OpenClaw , Access Control Bypass in OpenClaw
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 6.9, Medium |
|---|---|
| Actively exploited? | No |
| Affected | Nuxt-modules og-image (< 6.2.5) |
| Fixed in | 6.2.5 |
| Type (CWE) | CWE-400: CWE-400: Uncontrolled Resource Consumption |
CVE-2026-34404 is a nuxt og image vulnerable to dos via image generation in Nuxt-modules og-image. The fix is to upgrade to 6.2.5 and apply the runnable commands below.
What is CVE-2026-34404?
Nuxt OG Image generates OG Images with Vue templates in Nuxt. Prior to version 6.2.5, the image‑generation component by the URI: /_og/d/ (and, in older versions, /og-image/) contains a Denial of Service (DoS) vulnerability. The issue arises because there is no restriction on the width and height parameters of the generated image.
In practical terms, a successful attacker gets a denial-of-service condition that crashes or hangs the affected service. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.
Am I affected?
You are affected if you run Nuxt-modules og-image at a version listed in the Affected row above. Probe your installed build with the commands below.
# Confirm the installed version via your package manager
dpkg -l | grep -i og-image # Debian/Ubuntu
rpm -qa | grep -i og-image # RHEL/CentOS/Rocky
How to fix CVE-2026-34404
The primary fix is to upgrade to the patched build listed in the Fixed in row above (6.2.5). Pick the platform that matches your install and run the commands below.
Linux (Ubuntu / Debian)
sudo apt-get update
sudo apt-get install --only-upgrade og-image
# Confirm the installed version meets or exceeds 6.2.5
dpkg -s og-image | grep ^Version
Linux (RHEL / CentOS / Rocky)
sudo dnf upgrade --security og-image -y
rpm -q og-image
Windows (PowerShell, admin)
winget upgrade --id 'Nuxtmodules.ogimage' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\ogimage-6.2.5.msi" -ArgumentList '/qn /norestart' -Wait
PowerShell script (Windows): detect, back up, upgrade, verify, log
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\ogimage-Patch-CVE-2026-34404.log"
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Tee-Object -FilePath $log -Append }
Write-Log "Starting CVE-2026-34404 remediation for Nuxt-modules og-image"
# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*og-image*' } |
Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"
if (-not $installed) {
Write-Log "Product not installed on this host; nothing to do."
return
}
if ([version]$installed -ge [version]'6.2.5') {
Write-Log "Already at fixed version $installed; no action needed."
return
}
# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\ogimage-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Nuxt-modules\og-image"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"
# 3. Apply the patched installer
$installer = "$env:TEMP\ogimage-6.2.5.msi"
if (-not (Test-Path $installer)) {
throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"
# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
Where-Object { $_.Name -like '*og-image*' } |
Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'6.2.5') {
Write-Log "SUCCESS: now at $verify (>= 6.2.5)"
} else {
Write-Log "FAILURE: still at $verify after install"
exit 1
}
Bash script (Linux): detect, back up, upgrade, verify, log
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/og-image-patch-cve-2026-34404.log
log() { echo "$(date -Iseconds) $*" | tee -a "$LOG"; }
log "Starting CVE-2026-34404 remediation for Nuxt-modules og-image"
# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s og-image >/dev/null 2>&1; then
CURRENT=$(dpkg-query -W -f='${Version}' og-image)
PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q og-image >/dev/null 2>&1; then
CURRENT=$(rpm -q --queryformat '%{VERSION}' og-image)
PKG_MGR=dnf
else
log "og-image not installed via apt or rpm; check your package manager or vendor instructions."
exit 0
fi
log "Detected: og-image=$CURRENT (manager=$PKG_MGR)"
# 2. Backup config
BACKUP=/var/backups/og-image-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/og-image /etc/${pkg%%-*} ; do
[ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done
# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
sudo apt-get update -y
sudo apt-get install --only-upgrade -y og-image
else
sudo dnf upgrade --security -y og-image
fi
# 4. Verify
if [ "$PKG_MGR" = apt ]; then
NEW=$(dpkg-query -W -f='${Version}' og-image)
else
NEW=$(rpm -q --queryformat '%{VERSION}' og-image)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against 6.2.5 and restart the affected service if needed."
If you cannot patch immediately
These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.
Rate-limit and watchdog the affected service
sudo iptables -A INPUT -p tcp --dport 443 -m conntrack --ctstate NEW -m limit --limit 50/s -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -m conntrack --ctstate NEW -j DROP
How to verify the fix worked
Run the version probe again and confirm the running build matches the Fixed in row above.
dpkg -l | grep -i "og-image" # Debian/Ubuntu
rpm -qa | grep -i "og-image" # RHEL/CentOS/Rocky
Expected output: the package version should meet or exceed 6.2.5.
Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-34404 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.
Frequently asked questions
Is CVE-2026-34404 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-34404?
CVSS rates it 6.9 (Medium). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take og-image offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-34404 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://github.com/nuxt-modules/og-image/security/advisories/GHSA-c7xp-q6q8-hg76
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-34404
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor advisory before applying changes in production.*