CVE-2020-26282: BrowserUp Proxy allows you to manipulate HTTP requests and responses, capture HTTP content, and export perform

Q: How do I fix CVE-2020-26282?

browserup proxy: upgrade to 2.1.2. Exact commands for each OS are on this page.

Q: Is CVE-2020-26282 being exploited?

CVE-2020-26282 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-26282 affect?

CVE-2020-26282 affects browserup proxy. Severity is critical (CVSS 10.0). BrowserUp Proxy allows you to manipulate HTTP requests and responses, capture HTTP content, and export performance data as a HAR file. BrowserUp Proxy works well as a standalone proxy server, but it is especially useful when embedded in Sel

Q: How urgent is CVE-2020-26282?

Priority 68/100. Critical severity; EPSS top 8%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 10.0REMOTEUPGRADE

CVE-2020-26282 is a critical-severity flaw (CVSS 10.0) affecting browserup proxy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

BrowserUp Proxy allows you to manipulate HTTP requests and responses, capture HTTP content, and export performance data as a HAR file. BrowserUp Proxy works well as a standalone proxy server, but it is especially useful when embedded in Selenium tests. A Server-Side Template Injection was identified in BrowserUp Proxy enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability.

Why this priority

Critical severity
EPSS top 8%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	10.0 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	4.8% (top 8%)
CISA exploited list	No
Weakness	CWE-74
Published	2020-12-24
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: browserup

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-12-24 21:15 UTCPublished CVE record published
2026-06-17 03:07 UTCUpdated Record last modified

browserup browserup proxy UPGRADE

Affected: < 2.1.2

Fixed in: 2.1.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy browserup-proxy || rpm -q browserup-proxy || browserup-proxy --version

2. UPGRADE to 2.1.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade browserup-proxy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade browserup-proxy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-26282?

browserup proxy: upgrade to 2.1.2. Exact commands for each OS are on this page.

Is CVE-2020-26282 being exploited?

CVE-2020-26282 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-26282 affect?

CVE-2020-26282 affects browserup proxy. Severity is critical (CVSS 10.0). BrowserUp Proxy allows you to manipulate HTTP requests and responses, capture HTTP content, and export performance data as a HAR file. BrowserUp Proxy works well as a standalone proxy server, but it is especially useful when embedded in Sel

How urgent is CVE-2020-26282?

Priority 68/100. Critical severity; EPSS top 8%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

References

← Back to latest CVEs