Pega Robot Studio CVE-2026-0898

Pega Robot Studio developers using Browser Extension versions 22.1 or R25 must be deceived into visiting a malicious website during interrogation mode in Robot Studio on Chrome or Edge. Requires victim interaction (visiting malicious site).

While CVSS and EPSS scores are not publicly available, the real-world risk is moderate to high within the affected population. The attack vector is network-based (requires visiting a malicious website) but requires user interaction and specific conditions (interrogation mode enabled during development). The impact is severe: arbitrary file writes can lead to code execution, credential theft, or supply-chain compromise if a developer's automation scripts are checked into repositories. The vulnerability is not listed in the KEV catalog and no public proof-of-concept is referenced, suggesting limited active exploitation in the wild at present. However, the targeted nature (specifically Pega Robot Studio developers) and the requirement for social engineering (deceiving developers to visit a site) may explain low public visibility. Organizations using Pega for RPA should prioritize patching development environments, as a compromised developer workstation could introduce malicious code into production automation workflows.

A Pega Robot Studio developer receives a social engineering email or Slack message with a link to what appears to be documentation or a helpful automation resource. Upon clicking the link while Robot Studio is running in interrogation mode, the developer visits an attacker-controlled website that contains malicious JavaScript. The malicious script leverages the Pega Browser Extension's insufficient access controls to write a backdoored automation script directly to the developer's project directory, which is then committed to version control. The backdoor subsequently executes in the production Robot Runtime environment, enabling the attacker to exfiltrate sensitive data or manipulate business processes.