Skip to main content
Menu
CVEs

Etherpad unauthenticated file read in plugin asset handler

Etherpad 1.8.14 through 3.3.2 in a default production deployment, such as the Docker image or a systemd source install on Linux, is affected. Fixed in 3.3.3.

CVE-2026-114516Published November 19, 2026, updated

9.8CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 3.3.3
Who is exposed
Default setups

Summary

Etherpad, a real-time collaborative editor, has a path handling flaw in its plugin asset handler that lets a remote attacker read any file the Etherpad process can access. The attack works over the network without logging in and needs no action from a user.

Written by a model

Original description

Etherpad is a real-time collaborative editor. From 1.8.14 until 3.3.3, the pre-authentication /static/* plugin asset handler in src/node/utils/Minify.ts performs a backslash-to-forward-slash conversion after src/node/utils/sanitizePathname.ts has completed its POSIX path checks. On POSIX systems the sanitizer correctly treats backslashes as ordinary filename bytes, but the later conversion turns encoded backslash-separated parent-directory segments into traversal components without revalidation or containment. The expressPreSession registration and the always-present ep_etherpad-lite core pseudo-plugin make this path reachable without credentials, allowing a remote attacker to read any file available to the Etherpad process. Disclosed configuration or environment secrets can expose administrator credentials, after which the administrator plugin installer can provide in-process code execution and full server compromise. This issue is fixed in version 3.3.3.

Who should check

Operators running Etherpad 1.8.14 through 3.3.2 on Linux or other POSIX systems, including Docker image and systemd source installs, especially any exposed to untrusted networks.

Not fixed by: A reverse proxy does not mitigate it.

“works on Linux, e.g. the Docker image or a systemd source install”

github.com

What to do

  1. Check every install: default setups are affected.

  2. Upgrade to a fixed version: 3.3.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-114516 (Etherpad: Pre-auth arbitrary file read), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-114516 (entry last updated 2026-11-19):
Affected:
- ether etherpad: from 1.8.14, fixed in 3.3.3
Fixed versions: 3.3.3.
Conditions (all must be true for the bug to be hit):
- Etherpad versions 1.8.14 through 3.3.2 are affected. (source: https://github.com/ether/etherpad/security/advisories/GHSA-mc8w-wjhw-45x5)
- Default production deployment with no special configuration. (source: https://github.com/ether/etherpad/security/advisories/GHSA-mc8w-wjhw-45x5)
- Runs on a POSIX system such as Linux. (source: https://github.com/ether/etherpad/security/advisories/GHSA-mc8w-wjhw-45x5)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-114516 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-114516 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ether/etherpad/security/advisories/GHSA-mc8w-wjhw-45x5
- https://github.com/ether/etherpad/pull/8081
- https://github.com/ether/etherpad/commit/9c8d16d50e2fdfd9693ab35c43280410cb4db2fc
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-114516
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-114516"}.

Affected versions

cve.now Index

32Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.8/10CVSS 9.8
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · ether/etherpad · Advisory GHSA-mc8w-wjhw-45x5
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-114516
RecordNVD · CVE-2026-114516
Other links 2
RepositoryGitHub · ether/etherpad · Pull request #8081
RepositoryGitHub · ether/etherpad · Commit 9c8d16d5

Questions about CVE-2026-114516

Is CVE-2026-114516 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Without logging in, a remote party can read any file the Etherpad process user can read, such as settings.json, credentials.json, /proc/self/environ or /etc/passwd. This can lead to admin access and remote code execution.

Source: github.com

Which versions are affected by CVE-2026-114516?

etherpad: from 1.8.14 before 3.3.3.

Source: cve.now feed data

Am I affected, and how do I check?

Etherpad versions 1.8.14 through 3.3.2 are affected, in a default production deployment with no special configuration, and the advisory says it works on POSIX systems such as Linux. Check the installed Etherpad version to see where a deployment falls in that range.

Source: github.com

How do I fix CVE-2026-114516?

Upgrade Etherpad to 3.3.3, which is the fixed version listed for this vulnerability.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.