How to Fix CVE-2026-35253: Origin Validation Error in Oracle Macaron Tool of Oracle Open Source Projects
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-21978: Critical Vulnerability in Oracle FLEXCUBE Universal Banking — Critical Vulnerability in Oracle FLEXCUBE Universal Banking
- How to Fix CVE-2026-34319: Observable response discrepancy in MySQL Shell — Observable response discrepancy in MySQL Shell
- How to Fix CVE-2026-34277: PeopleSoft Enterprise PeopleTools (Bundle Sibling) , PeopleSoft Enterprise PeopleTools (Bundle Sibling)
- How to Fix CVE-2026-21977: Critical Vulnerability in Oracle Zero Data Loss Recovery Appliance Software , Critical Vulnerability in Oracle Zero Data Loss Recovery Appliance Software
- How to Fix CVE-2026-35250: Access control in Oracle VM VirtualBox , Access control in Oracle VM VirtualBox
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
CVE-2026-35253 is a origin validation error in Oracle Macaron Tool of Oracle Open Source Projects from Oracle Corporation. Upgrade to the patched build named in the Oracle Corporation advisory. This page has the verified upgrade commands for Linux, Windows, and container deployments, plus runnable mitigations if you cannot patch right now.
| Severity | CVSS 4.7 - Medium |
|---|---|
| Actively exploited? | Not listed on CISA KEV at time of writing |
| Affected | Oracle Macaron Tool of Oracle Open Source Projects: v0.22.0 |
| Fixed in | See vendor advisory for the patched build |
| Type (CWE) | CWE-346 Origin Validation Error |
What is CVE-2026-35253?
CVE-2026-35253 is a origin validation error in Oracle Macaron Tool of Oracle Open Source Projects. Vulnerability in the Oracle Macoron Tool product of Oracle Open Source Projects. The supported versions that is affected is v0.22.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Macaron Tool. Full technical detail is in the vendor advisory and the NVD entry.
Why this CVE matters
The origin validation error class of flaw against Oracle Macaron Tool of Oracle Open Source Projects is the kind of issue attackers chain into broader access once they get a foothold. Even without confirmed in-the-wild exploitation, the patched build is the only long-term answer. Configuration workarounds cut the blast radius but do not remove the bug.
Am I affected?
Run the version check that matches your platform. If the installed build sits inside the affected range from the table above, the fix applies to you.
# Linux package check
dpkg -s oraclemacarontooloforacleopensourceprojects 2>/dev/null | grep -i version # Debian / Ubuntu
rpm -q oraclemacarontooloforacleopensourceprojects 2>/dev/null # RHEL / Rocky
How to fix CVE-2026-35253
Apply the patched build the vendor names in the advisory. The commands below are starting points keyed to common platforms; adapt the package name and target version to your environment.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade oraclemacarontooloforacleopensourceprojects
dpkg -s oraclemacarontooloforacleopensourceprojects | grep -i version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh oraclemacarontooloforacleopensourceprojects -y
rpm -q oraclemacarontooloforacleopensourceprojects
Container image
# Vendor advisory: https://www.oracle.com/security-alerts/all-oracle-cves-outside-other-oracle-public-documents.html
docker pull <your-registry>/oraclemacarontooloforacleopensourceprojects:<patched-tag>
docker build -t <your-app>:patched .
docker stop <your-app> && docker rm <your-app>
docker run -d --name <your-app> <your-app>:patched
PowerShell detect/upgrade/verify/log (Windows)
# CVE-2026-35253 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-35253-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }
try {
Write-Log "Detect: checking installed product"
$installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
Where-Object { $_.Name -match 'Oracle Macaron Tool of Oracle Open Source Projects' }
if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
Write-Log "Found version $($installed.Version)"
Write-Log "Backup: copying program files and registry hive"
$stamp = Get-Date -Format yyyyMMdd-HHmm
$backup = "C:\Backup\CVE-2026-35253-$stamp"
New-Item -ItemType Directory -Force -Path $backup | Out-Null
Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null
Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue
Write-Log "Verify: re-reading product version"
$after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Oracle Macaron Tool of Oracle Open Source Projects' }
Write-Log "Post-patch version: $($after.Version)"
if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
Write-Log "ERROR: $_"
throw
}
Bash detect/upgrade/verify/log (Linux)
#!/usr/bin/env bash
# CVE-2026-35253 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-35253-fix.log; }
log "Detect: current oraclemacarontooloforacleopensourceprojects version"
if command -v dpkg >/dev/null 2>&1; then
current=$(dpkg-query -W -f='${Version}' oraclemacarontooloforacleopensourceprojects 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' oraclemacarontooloforacleopensourceprojects 2>/dev/null || echo "not-installed")
else
current="unknown"
fi
log "Current: $current"
log "Backup: snapshotting config"
backup="/var/backups/cve-2026-35253-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/oraclemacarontooloforacleopensourceprojects ] && cp -a /etc/oraclemacarontooloforacleopensourceprojects "$backup/" || true
log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
sudo apt-get update -qq
sudo apt-get install -y --only-upgrade oraclemacarontooloforacleopensourceprojects
elif command -v dnf >/dev/null 2>&1; then
sudo dnf upgrade -y oraclemacarontooloforacleopensourceprojects
elif command -v yum >/dev/null 2>&1; then
sudo yum update -y oraclemacarontooloforacleopensourceprojects
fi
log "Verify: re-reading oraclemacarontooloforacleopensourceprojects version"
if command -v dpkg >/dev/null 2>&1; then
after=$(dpkg-query -W -f='${Version}' oraclemacarontooloforacleopensourceprojects)
else
after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' oraclemacarontooloforacleopensourceprojects)
fi
log "After: $after"
if [ "$after" != "$current" ]; then
log "SUCCESS: oraclemacarontooloforacleopensourceprojects upgraded"
else
log "WARN: version unchanged. Confirm the patched build is in your repository."
exit 1
fi
After the upgrade, restart any service that loads the patched binary so the new code is actually running.
If you can't patch immediately
Patching is the only durable fix. These mitigations cut exposure while the change window is scheduled. They do not remove the vulnerability.
Restrict network exposure (iptables / nftables)
# Replace 10.0.0.0/8 with your management network.
sudo iptables -I INPUT -p tcp --dport 443 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4
# nftables equivalent
sudo nft add rule inet filter input tcp dport 443 ip saddr != 10.0.0.0/8 drop
Web server / WAF rule (ModSecurity sample)
# Append to /etc/modsecurity/rules/local.conf and reload Apache.
SecRule REQUEST_URI "@rx (?:\.\./|%2e%2e/)" \
"id:900001,phase:1,deny,status:403,msg:'Path traversal attempt blocked'"
SecRule ARGS "@rx (?:union[\s/*]+select|select[\s/*]+.*from)" \
"id:900002,phase:2,deny,status:403,msg:'SQLi pattern blocked'"
sudo systemctl reload apache2 # or nginx
How to verify the fix worked
After applying the patched build, confirm the version string matches the fixed release named in the Oracle Corporation advisory.
dpkg -s oraclemacarontooloforacleopensourceprojects | grep -i version # Debian / Ubuntu
rpm -q oraclemacarontooloforacleopensourceprojects # RHEL / Rocky
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-35253. For internet-facing deployments that were unpatched during the disclosure window, review logs for the affected endpoints over the full exposure period and rotate any credentials the vulnerable process could touch.
Frequently asked questions
Is CVE-2026-35253 being exploited in the wild?
At time of writing, CVE-2026-35253 is not on CISA's KEV list. Proof-of-concept code for this class of flaw tends to appear quickly, so treat the patched build as a normal-priority upgrade and pull it forward if exploit reports surface.
What is the CVSS score for CVE-2026-35253?
The CVSS base score is 4.7 (Medium). Full vector detail is on the NVD entry.
Will a firewall rule or WAF signature fully mitigate CVE-2026-35253?
No. Network-layer filters slow opportunistic scanners and block a subset of payloads, but a focused attacker who knows the bug will work around them. The vendor patch is the only durable fix.
Do I need to assume compromise if the affected service was internet-facing and unpatched?
Not automatically, but log review is cheap insurance. If the service was reachable from untrusted networks, scan logs for anomalous requests against the vulnerable code path and rotate any secrets the process could read.
References
- Official vendor advisory: https://www.oracle.com/security-alerts/all-oracle-cves-outside-other-oracle-public-documents.html
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-35253
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
*Assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*