How to Fix CVE-2026-24324: Denial of Service in SAP BusinessObjects Business Intelligence Platform (AdminTools)
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-39976: Authentication bypass in passport — Authentication bypass in passport
- How to Fix CVE-2026-3719: Tsinghua Unigroup Electronic Archives System downLoad path traversal — Tsinghua Unigroup Electronic Archives System downLoad path traversal
- How to Fix CVE-2026-0821: Path Traversal in quickjs , Path Traversal in quickjs
- How to Fix CVE-2026-1471: Caching of authentication context in Enterprise edition , Caching of authentication context in Enterprise edition
- How to Fix CVE-2026-6813: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripti , Improper Neutralization of Input During Web Page Generation ('Cross-site Scripti
*By Sai Kiran Pandrala*
| Severity | CVSS 6.5 - Medium |
|---|---|
| Actively exploited? | Not currently listed in CISA KEV |
| Affected | ENTERPRISE 430, 2025, 2027 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-405: Asymmetric Resource Consumption |
What is CVE-2026-24324?
CVE-2026-24324 is a denial of service flaw in SAP BusinessObjects Business Intelligence Platform (AdminTools). A crafted request triggers a code path that crashes or hangs the service, taking the product offline for legitimate users. Vendor description: SAP BusinessObjects Business Intelligence Platform (AdminTools) allows an authenticated attacker with user privileges to execute a specific query in AdminTools that could cause the Content Management Server (CMS) to crash, rendering the CMS partially or completely unavailable and resulting in the denial of service of the Content Management Server (CMS). Successful exploitation impacts system availability, while confidentiality and integrity remain unaffected.
Why this CVE matters
Denial-of-service flaws in a network gateway or firewall have an outsize operational impact. A single packet that reboots an inline device takes down everything behind it, which is why even non-RCE bugs on these products warrant priority patching.
For deployments of SAP BusinessObjects Business Intelligence Platform (AdminTools) that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.
Am I affected?
You are affected if your installation matches any of these version ranges:
- SAP BusinessObjects Business Intelligence Platform (AdminTools): ENTERPRISE 430
- SAP BusinessObjects Business Intelligence Platform (AdminTools): 2025
- SAP BusinessObjects Business Intelligence Platform (AdminTools): 2027
Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.
Open SAP BusinessObjects Business Intelligence Platform (AdminTools)'s About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.
How to fix CVE-2026-24324
- Read the vendor advisory in full: https://me.sap.com/notes/3695912
- Upgrade SAP BusinessObjects Business Intelligence Platform (AdminTools) to the patched build listed in the vendor advisory.
- Back up the configuration (and database, where applicable) before upgrading.
- Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
- Restart the affected service so the patched binary loads, then verify the new version (see verification section).
Apply the vendor patch
# Target fixed version: see advisory (https://me.sap.com/notes/3695912)
# Source advisory: https://me.sap.com/notes/3695912
# Product: SAP BusinessObjects Business Intelligence Platform (AdminTools) (SAP_SE)
# 1. Locate any installed build of SAP BusinessObjects Business Intelligence Platform (AdminTools) on the host.
dpkg -l 2>/dev/null | grep -i sap-businessobjects-business-intelligence-platform--admintools
rpm -qa 2>/dev/null | grep -i sap-businessobjects-business-intelligence-platform--admintools
# 2. The vendor does not publish through standard distro repos for most
# products. Download the patched installer / package from the advisory URL:
# https://me.sap.com/notes/3695912
# Verify the signature or SHA-256 the vendor publishes alongside it.
# 3. Apply the vendor installer (example - adjust extension per platform).
# .deb: sudo dpkg -i sap-businessobjects-business-intelligence-platform--admintools-<patched-version>.deb
# .rpm: sudo rpm -Uvh sap-businessobjects-business-intelligence-platform--admintools-<patched-version>.rpm
# .tar.gz: tar xzf sap-businessobjects-business-intelligence-platform--admintools-<patched-version>.tar.gz && sudo ./install.sh
# 4. Restart the affected service so the patched binary loads.
sudo systemctl restart sap-businessobjects-business-intelligence-platform--admintools 2>/dev/null || true
# 5. Confirm the running version matches the fixed version.
sap-businessobjects-business-intelligence-platform--admintools --version 2>/dev/null || true
# Windows admin workstation - try winget first if the vendor publishes there.
winget search 'SAP BusinessObjects Business Intelligence Platform (AdminTools)'
winget upgrade --id 'SAP BusinessObjects Business Intelligence Platform (AdminTools)' --silent --accept-source-agreements --accept-package-agreements
# Otherwise download the vendor's signed installer from the advisory URL above,
# verify its Authenticode signature, then install silently.
Get-AuthenticodeSignature "$env:TEMP\sap-businessobjects-business-intelligence-platform--admintools-patched.msi" | Format-List
Start-Process -FilePath "$env:TEMP\sap-businessobjects-business-intelligence-platform--admintools-patched.msi" -ArgumentList '/qn /norestart' -Wait
# Confirm via Get-Package.
Get-Package | Where-Object { $_.Name -match 'SAP BusinessObjects Business Intelligence Platform (AdminTools)' }
# Fleet check: re-scan with your vulnerability scanner.
# (Nessus, Qualys, Tenable, OpenVAS) - confirm the scanner no longer flags CVE-2026-24324.
Verify the fix landed
# 1. Confirm the running version matches the fixed-in version listed above.
# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
# The scanner should no longer flag this CVE on the patched target.
# 3. Inspect recent service / kernel logs for crash-loops or rollback events.
journalctl --since "10 minutes ago" | tail -50
dmesg --since "10 minutes ago" 2>/dev/null | tail -50
If you cannot patch immediately
Front the service with rate limiting and drop malformed packets at a load balancer or IPS. Patch to remove the underlying crash condition.
How to verify the fix worked
- After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
- Confirm the patched build matches the version listed in the vendor advisory.
- Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-24324.
- Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
- Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.
If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one.
Frequently asked questions
Is CVE-2026-24324 being exploited in the wild?
Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.
Will a WAF or IDS rule fully mitigate CVE-2026-24324?
No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.
How long should I plan for the upgrade?
Typical vendor-documented upgrade windows for SAP BusinessObjects Business Intelligence Platform (AdminTools) run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.
References
- Official vendor advisory: https://me.sap.com/notes/3695912
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-24324
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional vendor or research reference: https://url.sap/sapsecuritypatchday
*This guide was 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.*