Skip to main content

SAP BusinessObjects EUVDEUVD-2026-55880

| CVE-2026-66763 HIGH
Use of Hard-coded Cryptographic Key (CWE-321)
2026-08-11 sap GHSA-jwqg-65mh-q989
7.9
CVSS 3.1 · Vendor: sap
Share

Severity by source

Vendor (sap) PRIMARY
7.9 HIGH
AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
vuln.today AI
7.9 HIGH

Local access and high privileges required to reach the CMS store; scope change justified because recovered credentials enable compromise of connected external systems.

3.1 AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Primary rating from Vendor (sap).

CVSS VectorVendor: sap

Attack Vector
Local
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Analysis Generated
Aug 11, 2026 - 01:04 vuln.today
CVE Published
Aug 11, 2026 - 00:17 cve.org
HIGH 7.9

DescriptionCVE.org

SAP BusinessObjects Business Intelligence Platform stores certain sensitive credentials associated with user objects using a hard-coded cryptographic key. An attacker with high privileges and local access to the server could retrieve these objects and decrypt the stored credentials. Successful exploitation could allow the attacker to obtain sensitive authentication data and modify protected information, resulting in a high impact on confidentiality and integrity. There is no impact on availability.

AnalysisAI

SAP BusinessObjects Business Intelligence Platform (Central Management Server) protects user credential objects with a hard-coded cryptographic key, enabling a high-privileged local attacker to retrieve those objects and decrypt their contents. Affected versions include ENTERPRISE 430, 2025, and 2027 of the CMS component. No public exploit or active exploitation has been identified at time of analysis, but the CVSS scope change (S:C) signals that successfully decrypted credentials can be used to compromise systems beyond the BI platform itself.

Technical ContextAI

CWE-321 (Use of Hard-coded Cryptographic Key) describes the root cause: the application embeds a fixed, static key in its binary to encrypt sensitive credential data associated with user objects in the Central Management Server. Because the key is hard-coded rather than derived from a per-installation secret or HSM, any attacker who can access the stored credential objects and locate the key in the application binaries - through reverse engineering or published research - can decrypt them without guessing or brute-forcing. The affected component per CPE (cpe:2.3:a:sap_se:sap_businessobjects_business_intelligence_platform_(central_management_server):*:*:*:*:*:*:*:*) is the CMS, which serves as the central repository for user accounts, authentication data, and permissions within the SAP BO ecosystem. The CMS database therefore represents a high-value target for insider threats and compromised privileged accounts.

RemediationAI

Apply the patch documented in SAP Security Note 3756565, accessible via the SAP Support Portal at https://me.sap.com/notes/3756565. SAP's Security Patch Day page (https://url.sap/sapsecuritypatchday) provides broader patch-cycle context. While exact patched version numbers are not independently confirmed from available data beyond the SAP advisory, the note covers ENTERPRISE 430, 2025, and 2027 lines. As compensating controls pending patching: restrict local OS-level and database-level access to the CMS host to only those accounts that operationally require it - this directly limits the PR:H+AV:L attack path. Audit privileged account membership on CMS servers and enable logging of access to the CMS credential store. Force rotation of all credentials stored in the CMS after patching to invalidate any that may have been previously decrypted. These controls carry the trade-off of increased operational overhead for legitimate admin workflows.

Share

EUVD-2026-55880 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy