How to Fix CVE-2026-29062: Resource exhaustion in jackson-core
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-29062 is a resource exhaustion in FasterXML jackson-core. The fix is to apply the vendor patch noted below.
| Severity | 8.7 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | jackson-core >= 3.0.0, < 3.1.0 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-770: Allocation of Resources Without Limits or Throttling |
What is CVE-2026-29062?
jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. From version 3.0.0 to before version 3.1.0, the UTF8DataInputJsonParser, which is used when parsing from a java.io.DataInput source, bypasses the maxNestingDepth constraint (default: 500) defined in StreamReadConstraints. A similar issue was found in ReaderBasedJsonParser. This allows a user to supply a JSON document with excessive nesting, which can cause a StackOverflowError when the structure is processed, leading to a Denial of Service (DoS). This issue has been patched in version 3.1.0. The CVSS base score is 8.7 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://github.com/FasterXML/jackson-core/security/advisories/GHSA-6v53-7c9g-w56r.
Am I affected?
Check the version of jackson-core you are running and compare it against the Affected row above (jackson-core >= 3.0.0, < 3.1.0). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s jackson-core 2>/dev/null | grep -i ^Version
rpm -q jackson-core 2>/dev/null
command -v jackson-core >/dev/null && jackson-core --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*jackson-core*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "jackson-core" 2>$null
How to fix CVE-2026-29062
Upgrade jackson-core to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade jackson-core
dpkg -s jackson-core | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh jackson-core -y
# or for older releases:
sudo yum update jackson-core -y
rpm -q jackson-core
SUSE / openSUSE
sudo zypper refresh
sudo zypper update jackson-core
rpm -q jackson-core
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-29062 affecting jackson-core
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-29062-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detect installed version"
$pkg = Get-Package -Name "*jackson-core*" -ErrorAction SilentlyContinue
if ($pkg) { $pkg | Format-Table Name, Version }
else { Write-Host "Not detected via Get-Package; try winget list" }
Write-Host "[2/4] Backup configuration"
$backup = "C:\Backup\jackson-core-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\jackson-core" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "jackson-core" --silent --accept-source-agreements --accept-package-agreements
if ($LASTEXITCODE -ne 0) {
# Fallback: pull latest via OS update channel
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verify the patched build"
winget list --name "jackson-core"
Write-Host "Patch applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-29062 affecting jackson-core
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-29062-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
dpkg -s jackson-core 2>/dev/null | grep -i ^Version || echo "jackson-core not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q jackson-core || echo "jackson-core not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-29062-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/jackson-core /etc/jackson-core.d /etc/jackson-core.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y jackson-core
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y jackson-core
elif command -v yum >/dev/null; then
yum update -y jackson-core
elif command -v zypper >/dev/null; then
zypper --non-interactive update jackson-core
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s jackson-core 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q jackson-core
fi
echo "Done. Restart any service that loaded the old library."
If you can't patch immediately
Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.
Restrict exposure with nftables (Linux)
# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Block at the host firewall (Windows)
New-NetFirewallRule -DisplayName "Block-CVE-2026-29062" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-29062"
Disable the affected service (Linux)
sudo systemctl stop jackson-core 2>/dev/null || true
sudo systemctl disable jackson-core 2>/dev/null || true
If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.
How to verify the fix worked
After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.
# Linux
dpkg -s jackson-core 2>/dev/null | grep -i ^Version
rpm -q jackson-core 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true
# Windows
Get-Package -Name "*jackson-core*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-24538: Critical Vulnerability in Omnipress — Critical Vulnerability in Omnipress
- How to Fix CVE-2026-28221: CWE-121: Stack-based Buffer Overflow in wazuh — CWE-121: Stack-based Buffer Overflow in wazuh
- How to Fix CVE-2026-25936: GLPI Vulnerable to Authenticated SQL Injection in glpi , GLPI Vulnerable to Authenticated SQL Injection in glpi
- How to Fix CVE-2026-29785: Critical Vulnerability in nats-server , Critical Vulnerability in nats-server
- How to Fix CVE-2026-33277: Improper neutralization of special elements used in an OS command ('OS Command Injection') , Improper neutralization of special elements used in an OS command ('OS Command Injection')
Is CVE-2026-29062 actively exploited?
There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.
Do I need to reboot after patching CVE-2026-29062?
For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.
What is the CVSS score for CVE-2026-29062?
8.7 (High). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N.
Where is the official advisory for CVE-2026-29062?
The vendor advisory is at https://github.com/FasterXML/jackson-core/security/advisories/GHSA-6v53-7c9g-w56r. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-29062.
References
- Official vendor advisory: https://github.com/FasterXML/jackson-core/security/advisories/GHSA-6v53-7c9g-w56r
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29062
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/FasterXML/jackson-core/pull/1554
- Additional reference: https://github.com/FasterXML/jackson-core/commit/8b25fd67f20583e75fb09564ce1eaab06cd5a902
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*