CVE-2026-0490VulnerabilityPublished 10 Feb 2026

CVE-2026-0490: SAP BusinessObjects BI Platform · Missing Authorization

Affects SAP BusinessObjects BI PlatformSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 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 35% 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-26.

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

1. Immediately restrict network access to SAP BusinessObjects BI Platform endpoints to trusted internal networks and VPNs, blocking all unnecessary external access. 2. Implement strict firewall rules and network segmentation to isolate SAP BI servers from untrusted networks and limit exposure. 3. Monitor network traffic for unusual or malformed requests targeting SAP BI endpoints, using intrusion detection/prevention systems with custom signatures if possible. 4. Apply SAP vendor patches or security updates promptly once released for the affected versions (ENTERPRISE 430, 2025, 2027). 5. Conduct regular audits of SAP BI platform configurations and access controls to ensure no unauthorized endpoints are exposed. 6. Educate IT and security teams about this vulnerability to enhance incident response readiness. 7. Consider deploying web application firewalls (WAF) with rules tailored to detect and block unauthorized requests to SAP BI endpoints. 8. Maintain up-to-date backups and disaster recovery plans to mitigate the impact of potential denial of service incidents.

Description

CVE-2026-0490 is a high-severity vulnerability in SAP BusinessObjects BI Platform that allows unauthenticated attackers to send crafted network requests to a trusted endpoint, bypassing authentication. This flaw leads to a denial of service by preventing legitimate users from accessing the platform, impacting availability but not confidentiality or integrity. The vulnerability affects multiple versions, including ENTERPRISE 430, 2025, and 2027. It requires no authentication or user interaction and can be exploited remotely over the network. Although no known exploits are currently in the wild, the high CVSS score of 7.5 reflects the significant availability impact. European organizations relying on SAP BusinessObjects for business intelligence and reporting are at risk of operational disruption. Mitigation involves applying vendor patches once available, restricting network access to trusted endpoints, and monitoring for unusual request patterns. Countries with high SAP adoption and critical industries using SAP BI platforms are most likely to be affected.

Impact

For European organizations, the primary impact of CVE-2026-0490 is operational disruption due to denial of service on SAP BusinessObjects BI Platform, which is widely used for critical business intelligence and reporting functions. This can lead to significant downtime, affecting decision-making processes, financial reporting, and operational analytics. Industries such as manufacturing, finance, telecommunications, and public sector entities that rely heavily on SAP BI platforms may experience degraded service availability, potentially causing cascading effects on business continuity. Although confidentiality and integrity are not directly compromised, the inability to access BI data can hinder compliance reporting and strategic planning. The attack's remote and unauthenticated nature increases the risk of widespread exploitation, especially in environments with exposed or poorly segmented SAP infrastructure. The absence of known exploits currently provides a window for proactive defense, but the high severity score underscores the urgency of addressing this vulnerability.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (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:39 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats