CVE-2026-39910
STACKIT IaaS API flaw lets attackers attach high-priv service accounts to VMs, bypassing tenants.
Is CVE-2026-39910 being exploited?
Not confirmed. CVE-2026-39910 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-39910?
CVE-2026-39910 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-39910?
Not known from our data. No patch reference has been recorded for CVE-2026-39910, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-39910 affect?
CVE-2026-39910 affects STACKIT IaaS API. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-39910?
Patch when released; tighten access controls and monitor API activity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated, low-priv attackers can escalate to full org compromise by attaching high-priv service accounts to VMs and querying Instance Metadata for OAuth2 tokens.
Immediate action required
- affected< 2026-05-28
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.