CVE-2026-27676 | SAP S4HANA OData Service 4CORE 109 Manage Technical Object Structures authorization
VulDBArchived Apr 14, 2026✓ Full text saved
A vulnerability, which was classified as problematic , has been found in SAP S4HANA OData Service 4CORE 109 . This impacts an unknown function of the component Manage Technical Object Structures . Performing a manipulation results in missing authorization. This vulnerability is reported as CVE-2026-27676 . The attack is possible to be carried out remotely. No exploit exists. To fix this issue, it is recommended to deploy a patch.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-357268 · CVE-2026-27676 · GCVE-0-2026-27676
SAP S4HANA ODATA SERVICE 4CORE 109 MANAGE TECHNICAL OBJECT STRUCTURES AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.2 $0-$5k 1.14+
Summaryinfo
A vulnerability, which was classified as problematic, was found in SAP S4HANA OData Service 4CORE 109. Affected is an unknown function of the component Manage Technical Object Structures. Executing a manipulation can lead to authorization. This vulnerability appears as CVE-2026-27676. The attack may be performed from remote. There is no available exploit. It is advisable to implement a patch to correct this issue.
Detailsinfo
A vulnerability has been found in SAP S4HANA OData Service 4CORE 109 and classified as problematic. This vulnerability affects some unknown functionality of the component Manage Technical Object Structures. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity. CVE summarizes:
Due to missing authorization checks in the SAP S/4HANA OData Service (Manage Technical Object Structures), an attacker could update and delete child entities via exposed OData services without proper authorization. This vulnerability results in a low impact on integrity, while confidentiality and availability are not impacted.
The advisory is shared for download at me.sap.com. This vulnerability was named CVE-2026-27676 since 02/23/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/14/2026).
Applying a patch is able to eliminate this problem.
Productinfo
Vendor
SAP
Name
S4HANA OData Service
Version
4CORE 109
License
commercial
Website
Vendor: https://www.sap.com/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (sap): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Patch
Status: 🔍
0-Day Time: 🔒
Timelineinfo
02/23/2026 CVE reserved
04/14/2026 +49 days Advisory disclosed
04/14/2026 +0 days VulDB entry created
04/14/2026 +0 days VulDB entry last update
Sourcesinfo
Vendor: sap.com
Advisory: me.sap.com
Status: Confirmed
CVE: CVE-2026-27676 (🔒)
GCVE (CVE): GCVE-0-2026-27676
GCVE (VulDB): GCVE-100-357268
scip Labs: https://www.scip.ch/en/?labs.20150716
Entryinfo
Created: 04/14/2026 08:03
Changes: 04/14/2026 08:03 (62)
Complete: 🔍
Cache ID: 99:5F0:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸