Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighPublic exploit

Privilege Escalation in AWS Research and Engineering Studio Session Creation

IdentifiersCVE-2026-5708CWE-915· Improperly Controlled Modification…

CVE-2026-5708 is a privilege-escalation vulnerability in the session creation component of AWS Research and Engineering Studio (RES) affecting versions prior to 2026.03. The flaw stems from improper control of user-modifiable attributes during session creation, described as unsanitized control of user-modifiable attributes. An authenticated remote attacker can send a crafted API request to manipulate those attributes and cause RES to grant access associated with the Virtual Desktop Host instance profile. This can extend the attacker's effective permissions beyond their intended role and enable interaction with additional AWS resources and services reachable through that instance profile.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated attacker to escalate privileges within RES, assume the Virtual Desktop Host instance profile permissions, and access or interact with connected AWS resources and services. Based on the provided CVSS context and bulletin summary, the resulting impact can be high across confidentiality, integrity, and availability, including unauthorized access to cloud resources, misuse of IAM-backed permissions, potential downstream compromise of attached services, data exposure, operational disruption, and broader cloud-environment abuse.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, apply the AWS-provided mitigation patch referenced in the vendor guidance. As a compensating control, restrict access to the vulnerable RES API surfaces to only trusted authenticated users, review and minimize permissions granted to the Virtual Desktop Host instance profile, and monitor for anomalous session-creation API requests or unexpected use of instance-profile-backed AWS actions. These measures reduce exposure but do not replace the vendor fix.

Remediation

Patch, then assume compromise.

Upgrade AWS Research and Engineering Studio to version 2026.03, which contains the vendor fix for CVE-2026-5708. For environments that cannot immediately upgrade, apply the corresponding mitigation patch provided by AWS. Organizations maintaining forked or derivative RES deployments should merge the upstream fix into their custom codebase and validate that session creation logic no longer permits unsafe user control over privileged attributes.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Amazon Web ServicesResearch And Engineering Studioapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.