What Happened
SAP disclosed CVE-2026-89111, a CVSS 10 OAuth2 SSRF flaw in Cloud SDK for Python that can expose application client credentials when an attacker controls a tenant subdomain, according to "SAP Discloses Critical CVSS 10 Flaw in Cloud SDK for Python Allowing OAuth2 Credential Theft." RealGround analysis: affected BTP integrations used by applications or AI agents could expose credentials and connected data. GitLab also disclosed CVSS 10 flaws that may enable unauthenticated code execution, creating possible secondary exposure through development pipelines, repositories, and deployment workflows, according to "Critical GitLab Flaw (CVSS 10.0) Could Allow Unauthenticated RCE Across 12 Years of Releases" and "GitLab Patches CVSS 10.0 Flaw That Could Let Unauthenticated Users Run Server Code." The Paperclip report describes authorization and import weaknesses that could expose sensitive data or enable privileged agent execution, according to "Critical Paperclip Flaw Allowed Admin Access, Code Execution." Prioritize inventory, patch verification, credential rotation where exposure is plausible, and review of AI-connected data paths; available reporting does not establish successful compro
Why This Matters
AI systems increasingly connect natural-language decisions to SaaS integrations, internal data, memory stores, API calls, and production workflows. A signal that appears narrow in a vendor report can become broader business risk when it intersects with autonomous tools or sensitive context.
RealGround Analysis
This trend increases exposure to indirect prompt injection, unauthorized tool execution, sensitive data disclosure, and weak human approval workflows for organizations deploying LLM agents or AI-enabled automation.
Recommended Actions
- Inventory AI applications and agents using SAP Cloud SDK for Python or connected BTP integrations, then upgrade to vendor-fixed versions.
- Validate tenant identifiers and rotate OAuth2 client secrets that may have been exposed through affected integrations.
- Identify GitLab instances supporting AI development or deployment and verify they run fixed releases, including 19.4.2, 19.3.5, or 19.2.8 where applicable.
- Review GitLab audit logs, CI/CD configurations, runners, artifacts, and downstream dependencies for unexpected changes.
- Classify sensitive data before it enters prompts, embeddings, or logs.
- Apply redaction and retention controls to model inputs and outputs.
- Restrict agent permissions with least-privilege tool scopes.
- Add human approval workflows for state-changing actions.
- Review SaaS integrations, memory persistence, and data access paths.
- Test prompt injection and indirect prompt injection scenarios before production rollout.
