How to Fix CVE-2026-35229: Access control in Oracle Database Server

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

What is CVE-2026-35229?

Vulnerability in the Java VM component of Oracle Database Server. Supported versions that are affected are 19.3-19.30 and 21.3-21.21. Easily exploitable vulnerability allows unauthenticated attacker with network access via Oracle Net to compromise Java VM. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Java VM accessible data.

Am I affected?

Run the version check that matches your platform:

# Linux
dpkg -s default-jdk 2>/dev/null | grep -i version
rpm -q default-jdk 2>/dev/null
default-jdk --version 2>/dev/null

Compare what you see against the Affected row above (Oracle Corporation Oracle Database Server 19.3 to <19.30, 21.3 to <21.21). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-35229

The primary fix is to upgrade Oracle Database Server to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: Oracle Database Server 19.30; Oracle Database Server 21.21.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade default-jdk
default-jdk --version 2>/dev/null || dpkg -s default-jdk | grep -i version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --security default-jdk -y
rpm -q default-jdk

SUSE / openSUSE

sudo zypper patch --category security
rpm -q default-jdk

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-35229 affecting Java
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-35229-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] Detecting installed version of Java"
    $pkg = winget list --id "Java" 2>$null
    Write-Host $pkg

    Write-Host "[2/4] Backing up configuration"
    $backup = "C:\Backup\Java-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Java" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Applying upgrade to Oracle Database Server 19.30; Oracle Database Server 21.21"
    winget upgrade --id "Java" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "Java"
    Write-Host "Fix 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-35229 affecting Java
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-35229-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
    dpkg -s default-jdk 2>/dev/null | grep -i version || echo "default-jdk not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q default-jdk || echo "default-jdk not installed via rpm"
fi

echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-35229-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/default-jdk /etc/default-jdk.d /etc/default-jdk.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Applying upgrade (target: Oracle Database Server 19.30; Oracle Database Server 21.21)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y default-jdk
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y default-jdk
elif command -v yum >/dev/null; then
    yum update -y default-jdk
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
    dpkg -s default-jdk 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q default-jdk
fi
echo "Done. Restart any running daemons that loaded the old library."

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network restriction (Linux, nftables)

# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Service-level fallback

# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop default-jdk
sudo systemctl disable default-jdk

How to verify the fix worked

# Linux
default-jdk --version 2>/dev/null || dpkg -s default-jdk | grep -i version
rpm -q default-jdk 2>/dev/null || true

# Windows
winget list | findstr /I "default-jdk"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above Oracle Database Server 19.30; Oracle Database Server 21.21. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Related fixes

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

• How to Fix CVE-2026-35250: Access control in Oracle VM VirtualBox — Access control in Oracle VM VirtualBox
• How to Fix CVE-2026-21944: Critical Vulnerability in Oracle Agile Product Lifecycle Management for Process — Critical Vulnerability in Oracle Agile Product Lifecycle Management for Process
• How to Fix CVE-2026-34271: MySQL Server (Bundle Sibling) , MySQL Server (Bundle Sibling)
• How to Fix CVE-2026-35236: Access control in MySQL Server , Access control in MySQL Server
• How to Fix CVE-2026-21968: Critical Vulnerability in MySQL Server , Critical Vulnerability in MySQL Server

Is CVE-2026-35229 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

7.5 (high). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

• Official vendor advisory: https://www.oracle.com/security-alerts/cpuapr2026.html
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35229

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