On this page (7 sections)

Etherpad, the open source real-time collaborative editor, has a critical flaw in the handler that serves plugin static files. According to the GitHub advisory, any remote user without credentials can read files on the server that the Etherpad process is allowed to read. The issue is tracked as CVE-2026-114516 and is fixed in version 3.3.3.

If you self-host Etherpad (for a team wiki, a classroom, an agency or a customer portal), treat this as an urgent upgrade. A file read can expose the admin password, and the advisory describes how that can lead to full server compromise.

What happened

The advisory describes an unauthenticated path traversal in Etherpad's /static/* route. The route is registered before the authentication middleware runs, so no login, session or special configuration is needed to reach it. The advisory says this applies to a default production deployment on Linux, including the Docker image and a systemd source install.

The advisory shows a publication date of October 27, 2026 and an update on November 20, 2026, while the CVE record lists a publication date of November 19, 2026. So far the only detailed source is the project's own advisory; the research contains no independent analysis and no report of attacks.

Technical details in plain terms

Path traversal means an attacker tricks a server into leaving the folder it meant to serve files from and reading something else. Defenders usually stop this by checking the requested path for parent-directory segments. Here the check itself behaved correctly, but a later step undid it.

  • Etherpad first runs the requested path through a sanitizer. On Linux and other POSIX systems, a backslash is an ordinary character in a filename, so the sanitizer sees no parent-directory segments and lets the path through.
  • The plugin asset code in Minify.ts then converts every backslash to a forward slash, a conversion the sanitizer deliberately limits to Windows. A code comment there wrongly assumed the sanitizer had already removed such sequences.
  • After that conversion, encoded backslash sequences become real parent-directory segments, and no second check or containment test happens before the file is read.
  • Per the advisory, Etherpad always registers its core pseudo-plugin, so the plugin branch of this code is reached on default deployments without any plugin being installed.

The practical result, per the advisory, is that a remote attacker can read any file available to the Etherpad process. We are deliberately not reproducing the request format here.

Why a file read can become a full compromise

The advisory notes that on a typical deployment the readable files include settings.json, credentials.json and the process environment, which contain the admin password. With an admin session, the admin plugin installer can be used to run code inside the Etherpad process. That chain turns an information disclosure into remote code execution, which is why the severity is rated critical.

Who is affected

The advisory lists Etherpad versions from 1.8.14 up to but not including 3.3.3 as affected. Exposure is highest for instances directly reachable from the internet, since no authentication is needed. Instances behind a VPN or an IP allowlist are less exposed, but anyone who can reach them on that network could still attempt the request.

The advisory's description and proof of concept focus on Linux and other POSIX systems. The research does not say whether Windows installs are affected, so treat that as unconfirmed and upgrade regardless.

How to check your exposure

First find out which version you run. If you installed from source, this command, run in the Etherpad install directory, prints the version line from package.json. Compare it with 3.3.3:

Show the Etherpad version from package.json (run in the Etherpad install directory)Shell
grep '"version"' package.json

If you use Docker, this command, run on the Docker host, lists each running container with its image. Look at the image tag for your Etherpad container and compare it with 3.3.3:

List running containers and their image tags (run on the Docker host)Shell
docker ps --format '{{.Names}} {{.Image}}'

Any version at or above 1.8.14 and below 3.3.3 needs the upgrade. A tag such as latest does not tell you the version, so confirm what the container actually runs.

What to do now

  1. Upgrade Etherpad to 3.3.3 or later. Follow your normal deployment method (a release checkout, a new Docker image or your usual package process).
  2. Until you can upgrade, restrict network access to the instance with a VPN, IP allowlist or firewall rule. Treat this as a stopgap, not a fix.
  3. Assume secrets on an exposed server may have been read. Rotate the admin password and any credentials stored in settings.json, credentials.json or environment variables (database passwords, API keys, session secrets).
  4. Review the installed plugins in the admin interface and remove any you do not recognize, since the admin plugin installer is the route to code execution described in the advisory.
  5. Search web server and reverse proxy logs for suspicious requests to /static/ (see the next section), and check the server for unexpected processes or new files if you find any.
  6. If you find signs of abuse, follow an incident process: isolate the host, rebuild from a clean image and rotate every secret the host could access.
Caution. Upgrading or restarting Etherpad interrupts active editing sessions. Schedule it, tell users first, and back up your pads and configuration before you change versions.

Detection and monitoring

The advisory's technique relies on encoded backslashes, which usually appear as %5C in access logs. This read-only search lists requests to /static/ that contain that encoding. The path shown is the common nginx default and is only an example; adjust it for Apache, your reverse proxy or your container logging. Hits are worth investigating, but no hits do not prove you were not targeted, because some setups do not log the raw URL:

Search an access log for encoded backslashes in /static/ requests (example nginx path, run on the…Shell
grep -i '/static/' /var/log/nginx/access.log | grep -i '%5c'

Also watch for admin sessions you did not start, unexpected plugin installs and unusual outbound connections from the Etherpad host. As general hardening, not something the advisory prescribes, a proxy or website firewall rule on suspicious encoded sequences in URL paths can add a layer, but it is no replacement for patching. See what a WAF is for what such rules can and cannot do.

To watch the public side of your instance, uptime and certificate monitoring helps you notice outages or unexpected changes after an upgrade. It does not detect this flaw; the version check above is what settles it. For wider habits, see our guide on checking whether a website is hacked.

Open questions

  • The research contains no independent confirmation and no report of in-the-wild exploitation. The advisory is the single detailed source, and the research shows no CISA KEV entry.
  • The advisory dates (published October 27, updated November 20) differ from the CVE record's November 19 publication date; the sources do not explain the gap.
  • The research does not state who assigned the 9.8 CVSS score.
  • The research does not say whether Windows installations are affected.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-114516 - GitHub Advisory Databasegithub.com
  • Etherpad
  • path traversal
  • CVE-2026-114516
  • arbitrary file read
  • npm