● Critical · CVSS 9.3

How to Fix CVE-2026-29000: Cwe-347 improper verification of cryptographic signature in pac4j-jwt

Q: What is the CVSS score for CVE-2026-29000?

9.3 (Critical). Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`.

Q: Where is the official advisory for CVE-2026-29000?

The vendor advisory is at [https://www.pac4j.org/blog/security-advisory-pac4j-jwt-jwtauthenticator.html](https://www.pac4j.org/blog/security-advisory-pac4j-jwt-jwtauthenticator.html). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-29000.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-29000 is a cwe-347 improper verification of cryptographic signature in pac4j pac4j-jwt. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	9.3 (Critical)
Actively exploited?	No public listing in CISA KEV
Affected	pac4j-jwt 4.0 to <4.5.9; pac4j-jwt 5.0 to <5.7.9; pac4j-jwt 6.0 to <6.3.3
Fixed in	See vendor advisory
Type (CWE)	CWE-347 Improper Verification of Cryptographic Signature

What is CVE-2026-29000?

pac4j-jwt versions prior to 4.5.9, 5.7.9, and 6.3.3 contain an authentication bypass vulnerability in JwtAuthenticator when processing encrypted JWTs that allows remote attackers to forge authentication tokens. Attackers who possess the server's RSA public key can create a JWE-wrapped PlainJWT with arbitrary subject and role claims, bypassing signature verification to authenticate as any user including administrators. The CVSS base score is 9.3 (Critical), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://www.pac4j.org/blog/security-advisory-pac4j-jwt-jwtauthenticator.html.

Am I affected?

Check the version of pac4j-jwt you are running and compare it against the Affected row above (pac4j-jwt 4.0 to <4.5.9; pac4j-jwt 5.0 to <5.7.9; pac4j-jwt 6.0 to <6.3.3). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s pac4j-jwt 2>/dev/null | grep -i ^Version
rpm -q pac4j-jwt 2>/dev/null
command -v pac4j-jwt >/dev/null && pac4j-jwt --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*pac4j-jwt*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "pac4j-jwt" 2>$null

How to fix CVE-2026-29000

Upgrade pac4j-jwt 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 pac4j-jwt
dpkg -s pac4j-jwt | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh pac4j-jwt -y
# or for older releases:
sudo yum update pac4j-jwt -y
rpm -q pac4j-jwt

SUSE / openSUSE


sudo zypper refresh
sudo zypper update pac4j-jwt
rpm -q pac4j-jwt

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-29000 affecting pac4j-jwt
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-29000-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 "*pac4j-jwt*" -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\pac4j-jwt-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\pac4j-jwt" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "pac4j-jwt" --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 "pac4j-jwt"
    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-29000 affecting pac4j-jwt
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-29000-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 pac4j-jwt 2>/dev/null | grep -i ^Version || echo "pac4j-jwt not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q pac4j-jwt || echo "pac4j-jwt not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-29000-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/pac4j-jwt /etc/pac4j-jwt.d /etc/pac4j-jwt.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 pac4j-jwt
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y pac4j-jwt
elif command -v yum >/dev/null; then
    yum update -y pac4j-jwt
elif command -v zypper >/dev/null; then
    zypper --non-interactive update pac4j-jwt
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s pac4j-jwt 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q pac4j-jwt
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-29000" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-29000"

Disable the affected service (Linux)


sudo systemctl stop pac4j-jwt 2>/dev/null || true
sudo systemctl disable pac4j-jwt 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 pac4j-jwt 2>/dev/null | grep -i ^Version
rpm -q pac4j-jwt 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 "*pac4j-jwt*" | 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

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-27496: Critical Vulnerability in n8n — Critical Vulnerability in n8n
How to Fix CVE-2026-28105: Unsafe deserialization in Good Energy — Unsafe deserialization in Good Energy
How to Fix CVE-2026-24466: Critical Vulnerability in See "References" section , Critical Vulnerability in See "References" section
How to Fix CVE-2026-40311: Use-after-free in ImageMagick , Use-after-free in ImageMagick
How to Fix CVE-2026-35636: Cwe-696: incorrect behavior order in OpenClaw , Cwe-696: incorrect behavior order in OpenClaw

Is CVE-2026-29000 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-29000?

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-29000?

9.3 (Critical). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N.

Where is the official advisory for CVE-2026-29000?

The vendor advisory is at https://www.pac4j.org/blog/security-advisory-pac4j-jwt-jwtauthenticator.html. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-29000.

References

Official vendor advisory: https://www.pac4j.org/blog/security-advisory-pac4j-jwt-jwtauthenticator.html
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29000
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://www.codeant.ai/security-research/pac4j-jwt-authentication-bypass-public-key
Additional reference: https://www.vulncheck.com/advisories/pac4j-jwt-jwtauthenticator-authentication-bypass

*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.*