Siebel CRM Integration EUVD-2026-61426

Network access via HTTPS to the Siebel CRM Integration REST API endpoint is required. No authentication is required for exploitation (CVSS PR:N), but the high attack complexity (AC:H) indicates exploitation is non-trivial - likely requiring precise request construction, specific knowledge of the target's Siebel API schema or authentication flow state, or exploitation of a particular sequence of REST interactions. Deployments that do not expose the Siebel CRM Integration REST component to untrusted networks are not directly reachable from external attackers. Versions outside the 17.0-26.6 range are not listed as affected. No user interaction is required (UI:N), and there is no scope change (S:U), meaning impact is bounded to the Siebel CRM Integration system itself.

The 7.4 CVSS base score reflects a genuinely high-severity issue: unauthenticated network access (AV:N, PR:N) paired with full confidentiality and integrity impact (C:H, I:H) and no availability impact (A:N). The AC:H modifier is the primary mitigating factor - exploitation is non-trivial and unlikely to be achieved by opportunistic scanners, but a motivated adversary with Siebel REST API knowledge could realistically succeed. The Authentication Bypass tag is a strong qualitative signal that the vulnerability class is well-understood and that exploitation paths may be discoverable through API documentation or reverse engineering. No CISA KEV listing and no known public exploit code exist at time of analysis, which reduces immediate mass-exploitation risk, but the absence of a KEV listing does not preclude targeted exploitation by threat actors with CRM data objectives. No EPSS score was available in the source data, limiting probabilistic forecasting. Even a mid-sized municipal IT team in swidnica running Siebel integrations should treat this as urgent given the potential for complete CRM data compromise without any credential requirement. The lack of an assigned CWE introduces moderate analytical uncertainty about the precise root cause.

An attacker with HTTPS network access to the Siebel CRM Integration REST API sends crafted requests that exploit a flaw in the authentication logic - potentially bypassing token validation or session enforcement - to interact with the API as if authenticated. The high attack complexity suggests the attacker must possess specific knowledge of the Siebel REST API structure or internal authentication state, making this more likely a targeted attack than opportunistic scanning. Once authentication is bypassed, the attacker can enumerate, exfiltrate, or tamper with all CRM data accessible to the integration layer, including customer records, business transactions, and configuration data. No public exploit code has been identified at time of analysis.