CVE-2026-0485VulnerabilityPublished 10 Feb 2026

CVE-2026-0485: SAP BusinessObjects BI Platform · Asymmetric Resource Consumption

Affects SAP BusinessObjects BI PlatformSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SAP_SESAP BusinessObjects BI Platform	Affected =2025 =2027	Fixed in–

AI-suggested

To mitigate CVE-2026-0485, European organizations should implement the following specific measures: 1) Deploy network-level access controls such as firewalls and intrusion prevention systems (IPS) to restrict and monitor incoming requests to the CMS, blocking suspicious or malformed traffic patterns indicative of exploitation attempts. 2) Implement rate limiting and request throttling on the CMS endpoints to prevent resource exhaustion from repeated crafted requests. 3) Restrict CMS access to trusted internal networks or VPNs, minimizing exposure to unauthenticated external actors. 4) Monitor CMS logs and network traffic for anomalies such as repeated crashes, restarts, or unusual request patterns that could signal exploitation attempts. 5) Engage with SAP support channels to obtain and apply any forthcoming patches or security updates addressing this vulnerability as soon as they become available. 6) Consider deploying application-layer gateways or web application firewalls (WAF) with custom rules tailored to detect and block exploit attempts targeting this vulnerability. 7) Conduct regular security assessments and penetration testing focused on SAP BusinessObjects environments to identify and remediate potential weaknesses. 8) Develop and test incident response plans specifically for SAP service disruptions to ensure rapid recovery and minimize business impact.

Description

CVE-2026-0485 is a high-severity vulnerability in SAP BusinessObjects BI Platform that allows unauthenticated attackers to cause a denial-of-service by crashing the Content Management Server (CMS) through specially crafted requests. Exploitation leads to repeated CMS crashes and automatic restarts, resulting in persistent service disruption and complete unavailability of the CMS. The vulnerability affects multiple versions including ENTERPRISE 430, 2025, and 2027. No confidentiality or integrity impact is reported, and no user interaction or authentication is required. Although no known exploits are currently in the wild, the ease of exploitation and high impact on availability make this a critical concern for organizations relying on SAP BusinessObjects for business intelligence operations. European organizations using these SAP versions should prioritize mitigation to prevent operational disruptions. Specific mitigations include network-level filtering, strict access controls, and monitoring for anomalous CMS requests. Countries with high SAP adoption and critical industries such as Germany, France, and the UK are most likely to be affected.

Impact

For European organizations, this vulnerability poses a significant risk to the availability of SAP BusinessObjects BI Platform services, which are critical for data analytics, reporting, and decision-making processes. A successful attack could cause prolonged outages of the CMS, disrupting business intelligence workflows and potentially delaying critical business operations. Industries relying heavily on SAP BI for regulatory reporting, financial analysis, or operational monitoring—such as banking, manufacturing, telecommunications, and public sector entities—may experience operational and reputational damage. The lack of confidentiality or integrity impact limits data breach risks, but the availability disruption alone can lead to financial losses and compliance challenges, especially under regulations like GDPR that mandate operational resilience. The ease of exploitation without authentication increases the threat surface, making external attackers or automated bots capable of launching denial-of-service attacks. Persistent service disruption could also affect supply chain partners and customers relying on timely business intelligence outputs. Given SAP's widespread adoption in Europe, the potential scale of impact is considerable.

Summary

CVE-2026-0485 is a vulnerability classified under CWE-405 (Asymmetric Resource Consumption) affecting SAP BusinessObjects BI Platform's Content Management Server (CMS). The flaw allows an unauthenticated attacker to send specially crafted requests that exploit resource consumption asymmetry, causing the CMS to crash and subsequently restart automatically. This cycle can be repeated indefinitely, leading to a persistent denial-of-service (DoS) condition that renders the CMS unavailable. The CMS is a core component responsible for managing content and metadata within the SAP BusinessObjects environment, and its unavailability disrupts business intelligence operations. The vulnerability affects multiple versions, including ENTERPRISE 430, 2025, and 2027, indicating a broad impact across recent SAP BusinessObjects deployments. The CVSS v3.1 score of 7.5 reflects high severity, with an attack vector of network (AV:N), no privileges required (PR:N), no user interaction (UI:N), and impact limited to availability (A:H) without affecting confidentiality or integrity. No patches or known exploits are currently reported, but the vulnerability's nature makes it a significant risk for service disruption. The attack requires no authentication, making it accessible to external threat actors. The vulnerability stems from improper handling of resource-intensive requests, leading to asymmetric resource consumption that overwhelms the CMS process. This can degrade service reliability and availability, impacting business continuity.

CWE-405Asymmetric Resource Consumption (Amplification) (opens in a new tab)
Class weakness
The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."
Architecture and Design
An application must make resources available to a client commensurate with the client's access level.
Architecture and Design
An application must, at all times, keep track of allocated resources and meter their usage appropriately.
System Configuration
Consider disabling resource-intensive algorithms on the server side, such as Diffie-Hellman key exchange.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Feb 2026, 09:52 UTC

WeaknessesCWE-405

Technical details

References

Community reviews

Related threats