CVE-2026-39910
Received Received - Intake
Missing Authorization Check in STACKIT IaaS API Leading to Full Organization Compromise

Publication date: 2026-06-08

Last updated on: 2026-06-08

Assigner: VulnCheck

Description
STACKIT IaaS API contains a missing authorization check vulnerability that allows authenticated, low-privileged attackers to escalate privileges to full organization compromise by attaching arbitrary service accounts to virtual machines they control. Attackers can exploit the unvalidated PUT servers service-accounts endpoint to attach high-privileged service accounts and query the Instance Metadata Service to retrieve OAuth2 tokens, bypassing tenant boundaries and gaining unauthorized control over the entire organization environment.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-08
Last Modified
2026-06-08
Generated
2026-06-09
AI Q&A
2026-06-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
stackit iaas_api to 2026-05-28 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-39910 is a critical vulnerability in the STACKIT IaaS API caused by a missing authorization check. It allows authenticated attackers with low privileges to escalate their access to full organization compromise. The attackers exploit an unvalidated PUT request to the servers service-accounts endpoint to attach high-privileged service accounts to virtual machines they control.

Once the high-privileged service accounts are attached, attackers can query the Instance Metadata Service to retrieve OAuth2 tokens. This bypasses tenant boundaries and grants unauthorized control over the entire organization environment.

Compliance Impact

The vulnerability allows attackers to escalate privileges and gain unauthorized control over the entire organization environment by bypassing tenant boundaries and attaching high-privileged service accounts to virtual machines they control.

Such unauthorized access and full organizational compromise can lead to exposure or misuse of sensitive data, which may violate compliance requirements under common standards and regulations like GDPR and HIPAA that mandate strict access controls and protection of personal and sensitive information.

Therefore, this vulnerability poses a significant risk to maintaining compliance with these regulations due to the potential for data breaches and unauthorized data access.

Impact Analysis

This vulnerability can lead to a complete takeover of your organization’s environment. An attacker with low privileges can escalate their access to full administrative control by attaching high-privileged service accounts to virtual machines they control.

With this unauthorized access, attackers can retrieve OAuth2 tokens and bypass tenant boundaries, potentially leading to data breaches, unauthorized resource manipulation, and disruption of services within your organization.

Detection Guidance

This vulnerability can be detected by monitoring for unauthorized PUT requests to the servers service-accounts endpoint in the STACKIT IaaS API. Specifically, look for attempts by low-privileged authenticated users to attach high-privileged service accounts to virtual machines they control.

Commands to detect such activity might include inspecting API logs for suspicious PUT requests targeting the service-accounts endpoint, for example using tools like curl or API gateway logs.

  • Check API access logs for PUT requests to the /servers/service-accounts endpoint.
  • Use commands like: curl -X PUT https://<stackit-api-endpoint>/servers/service-accounts -H "Authorization: Bearer <token>" to test if unauthorized service account attachment is possible.
  • Monitor virtual machine metadata service queries for OAuth2 tokens that should not be accessible to low-privileged users.
Mitigation Strategies

Immediate mitigation steps include upgrading the STACKIT IaaS API to a version later than 2026-05-28 where the missing authorization check vulnerability is fixed.

Additionally, restrict access to the servers service-accounts endpoint to only fully authorized users and monitor for suspicious activity involving service account attachments.

  • Apply the security patch or upgrade the STACKIT IaaS API to a fixed version.
  • Implement strict authorization checks on the service-accounts endpoint.
  • Audit and monitor API usage logs for unauthorized privilege escalation attempts.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-39910. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart