dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-1079

MEDIUM · 6.0 CVSS v4.0 Published 2026-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A native messaging host vulnerability in Pega Browser Extension (PBE) affects users of all versions of Pega Robotic Automation who have installed Pega Browser Extension. A bad actor could create a website that contains malicious code that targets PBE. The vulnerability could occur if a user navigates to this website. The malicious website could then present an unexpected message box.

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 confidence

The Pega Browser Extension contains a native messaging host vulnerability where the extension does not properly validate the origin of messages received from web pages. A malicious website can send specially crafted messages to the native messaging host component, causing it to display unexpected message boxes to the user.

MitigationUsers should avoid navigating to untrusted websites while the Pega Browser Extension is installed. Organizations should assess whether the Pega Browser Extension is required and consider disabling or removing it if unused, or implement additional browser-based restrictions.

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:N/VA:H/SC:N/SI:N/SA:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Pega Browser Extension is installed
    Open your browser's extension management page (chrome://extensions for Chrome, about:addons for Firefox) and look for 'Pega' or 'Pega Browser Extension' in the list of installed extensions.
    Affected if The extension appears in the browser's list of installed extensions.
  2. Identify the installed extension version
    In the browser's extension management page, locate the Pega Browser Extension and note the version number displayed. For Chrome, enable Developer mode to see version details. For Firefox, click on the extension to view its details.
    Affected if A version number is displayed for the Pega Browser Extension.
  3. Verify native messaging host configuration
    Check for native messaging host configuration files or registry entries. On Windows, look in the registry under HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\ or HKEY_LOCAL_MACHINE\Software\Google\Chrome\NativeMessagingHosts\ for entries containing 'Pega'. On macOS/Linux, check ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/ or /etc/chromium/native-messaging-hosts/.
    Affected if A native messaging host entry for Pega exists in the registry or as a manifest file.
  4. Locate the native messaging host executable
    If native messaging is configured, find the associated executable file. The registry entry or manifest file will contain a path to a .exe (Windows), .app (macOS), or binary (Linux) that serves as the native messaging host for Pega.
    Affected if A native messaging host executable file associated with Pega is found on the system.
  5. Compare installed version to any known affected versions
    Document the exact version number found in step 2. Since no specific version ranges are provided in the CVE, compare your version against any Pega release notes or security advisories related to CVE-2026-1079.
    Affected if The installed version matches or predates any version noted as vulnerable in official Pega documentation.

You are affected if the Pega Browser Extension is installed and the native messaging host component is enabled, regardless of version, since the vulnerability stems from missing origin validation in the native messaging implementation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should avoid navigating to untrusted websites while the Pega Browser Extension is installed. Organizations should assess whether the Pega Browser Extension is required and consider disabling or removing it if unused, or implement additional browser-based restrictions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1079 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1079 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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