CVE-2026-1078
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn arbitrary file-write vulnerability in Pega Browser Extension (PBE) affects Pega Robotic Automation version 22.1 or R25 users who are running automations that work with Google Chrome or Microsoft Edge. A bad actor could create a website that includes malicious code. The vulnerability could occur if a Robot Runtime user navigates to the malicious website.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceArbitrary file-write vulnerability in Pega Browser Extension (PBE) affecting Pega Robotic Automation v22.1 and R25. When a Robot Runtime user navigates to a malicious website in Chrome or Edge, the attacker can write arbitrary files to the local system through the vulnerable extension.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Pega Robotic Automation installationLook for Pega Robot Runtime or Pega Browser Extension in installed programs, or check common installation directories for Pega-related executables or DLLsAffected if Pega Robotic Automation software is present on the system
-
Check installed version against affected releasesLocate the version information for the Pega Robotic Automation installation (typically found in program files, registry, or application About/Help) and compare to v22.1 and R25Affected if Installed version is exactly v22.1 or R25, or falls within this release line
-
Verify browser extension presence in Chrome or EdgeOpen Chrome or Edge browser, navigate to extensions management (chrome://extensions or edge://extensions), and look for Pega Browser Extension or PBE listed as installedAffected if Pega Browser Extension is installed and enabled in Chrome or Edge
-
Confirm Robot Runtime is active or capable of loading the extensionCheck if Robot Runtime process is running or can be launched with the browser extension loaded; verify the extension is loaded when browsingAffected if Robot Runtime can run with the vulnerable browser extension loaded and active
System is affected if Pega Robotic Automation version 22.1 or R25 is installed with the Pega Browser Extension enabled in Chrome or Edge and the user can browse the web while Robot Runtime is active
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Pega Robotic Automation to vendor-provided patched version; advise users to avoid navigating untrusted websites while Robot Runtime is active with browser extensions loaded.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1078 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data