CVE-2026-0490
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSAP BusinessObjects BI Platform allows an unauthenticated attacker to craft a specific network request to the trusted endpoint that breaks the authentication, which prevents the legitimate users from accessing the platform. As a result, it has a high impact on the availability but no impact on the confidentiality and integrity.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSAP BusinessObjects BI Platform contains an authentication bypass vulnerability where an unauthenticated attacker can send a specific network request to a trusted endpoint that breaks the authentication mechanism, preventing legitimate users from accessing the platform.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 430= 2025= 2027CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed BusinessObjects versionAccess the SAP BusinessObjects Central Management Console (CMC) or use the SAP BusinessObjects Administration Tool to view the installed version. Alternatively, check the installation directory or the SAP BusinessObjects installation logs for the exact version number.Affected if The installed version matches 430, 2025, or 2027.
-
Locate the trusted endpointReview SAP BusinessObjects network configuration and documentation to identify the trusted authentication endpoint (typically exposed on the SAP BusinessObjects web application server). Consult the SAP BusinessObjects server configuration files for endpoint URLs.Affected if The trusted endpoint is exposed and accessible over the network without authentication.
-
Verify network accessibility of the endpointFrom an external or untrusted network location, attempt to send an HTTP/HTTPS request to the suspected trusted endpoint URL. Use network scanning tools to identify open ports and services associated with SAP BusinessObjects web interfaces.Affected if The trusted endpoint responds to network requests from untrusted locations.
-
Review authentication logs for anomaliesExamine SAP BusinessObjects authentication and system logs for signs of authentication mechanism failures, unusual authentication patterns, or spikes in failed login attempts that coincide with the timing of the specific network request pattern.Affected if Logs show unusual authentication failures or a sudden breakdown in the authentication mechanism after a specific network request.
A user is affected if the installed SAP BusinessObjects BI Platform version is 430, 2025, or 2027 and the trusted authentication endpoint is network-accessible, allowing an unauthenticated attacker to send requests that break the authentication mechanism.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the relevant SAP security patch for this vulnerability; until patched, implement network-level controls to restrict access to the trusted endpoint and monitor for anomalous authentication failures.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0490 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0490 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data