On this page (7 sections)

CVE-2026-129110 describes an authentication bypass in sysPass. According to the NVD entry, versions 3.0.1 through 3.2.11 let an unauthenticated attacker reinstall an instance that is already installed, and from there take control of it.

If you run sysPass and it is reachable from the internet or a wide internal network, treat this as urgent. The record is new and thin on detail, so this article separates what the source states from what is still unknown.

What was reported

The NVD description says the install/install handler can be reached by an unauthenticated POST request and never checks whether the application is already installed. In practice, a setup routine that should only run once on a fresh server can be run again on a live one.

The same description lists what a successful attacker could do: overwrite config.xml, point the application at a database the attacker controls, create an administrator account, and plant serialized PublicLink gadget chains that are triggered through account/viewLink to execute commands.

At the time of writing, CVE-2026-129110 has no full NVD record: no CVSS score, no CWE, no CISA KEV status and no listed references or patched version. Only one independent publisher covers the story. Details may change as the record is completed.

Why this class of bug is serious

Installers are meant to run once. When the installer endpoint stays reachable after setup and does not verify that setup already happened, anyone who can reach the web server can act as the owner of the application. No password, session or prior foothold is needed, which is why the NVD text frames it as an authentication bypass.

The impact chain described is also worse than a simple takeover. Replacing the configuration redirects the application to a database the attacker runs, so the attacker chooses what the app sees, including the administrator account. Serialized object payloads in a later step are described as leading to command execution. We are not describing exploit mechanics here, and the research does not provide any.

Who is exposed

  • Anyone running sysPass 3.0.1 through 3.2.11.
  • Instances whose web interface is reachable from the internet or from a wide internal network. Based on the description, the attacker needs only network access to the web application.
  • Admins who have not confirmed which sysPass version they run. Older installs are easy to forget.

The research does not say whether versions before 3.0.1 or after 3.2.11 are affected. Do not assume they are safe or unsafe; check the project's own release notes and advisories.

How to check your exposure

Start by finding your version and who can reach the application. Check the version in your deployment records or the application interface. If you installed from a Git checkout, this read-only command, run in the application directory, shows the checked-out tag or commit:

Show the current Git tag or commit of a sysPass checkout (run in the application directory)Shell
git describe --tags --always

If you deploy another way, for example from a container image, read the version from your deployment configuration instead. Next, search your web server access logs for requests to the installer path. This read-only search lists matching lines; legitimate traffic after setup should return none. The log path below is a common nginx default, so adjust it to your server:

Search an access log for requests to the install handler (adjust the log path)Shell
grep -i "install/install" /var/log/nginx/access.log

Also look for signs that a reinstall already happened: a changed modification time on config.xml, a database host you do not recognize in that file, administrator accounts nobody created, or unexpected requests to account/viewLink. This read-only command shows when the configuration file was last modified:

Show when the sysPass configuration file was last modified (replace the placeholder path)Shell
ls -l /path/to/config.xml

The path above is only a placeholder. Find where config.xml is stored in your own installation before relying on the result.

What to do now

  1. Inventory every sysPass instance and record its version. Anything from 3.0.1 to 3.2.11 is in scope.
  2. Restrict network access today: place the application behind a VPN, an IP allowlist or an authenticated reverse proxy so it is not open to the whole internet.
  3. If your web server supports it, block requests to the install/install path from outside until a fix is confirmed. Test this on a staging copy first so you do not break normal use.
  4. Check the official sysPass project for a patched release or advisory and upgrade as soon as one is available. The research does not name a fixed version.
  5. Review logs, config.xml, the configured database host and the administrator account list for signs of tampering.
  6. If you find any sign of tampering, assume stored credentials are compromised. Rotate the secrets kept in the instance, starting with the most privileged ones, and rebuild the server from a known-good state.
  7. Take a verified backup of the configuration and database before making changes, and store it offline.
Caution. Blocking paths or placing the app behind a proxy can lock out legitimate users. Change one thing at a time and keep console or SSH access available while you test.

Detection and monitoring afterwards

Keep the installer path on a watch list in your logging or alerting, since any request to it on a live instance is suspicious. Alert on changes to configuration files and on new administrator accounts. Because the described chain ends in command execution, also watch for new processes, cron entries or unexpected files under the web root.

A web application firewall can add a layer of filtering in front of an app like this; see what a WAF is for what it can and cannot do. For outside-in checks of your own domain, certificate and DNS changes, monitoring can alert you to unexpected changes, though it does not replace patching. If you suspect compromise, follow website hacked: what to do.

What we still do not know

  • The severity score and weakness classification, since NVD has not published them yet.
  • Which sysPass release fixes the issue, or whether a fix exists.
  • Whether the flaw is being exploited. Nothing in the research reports exploitation.
  • Whether versions outside 3.0.1 to 3.2.11 are affected.

Re-check the NVD record and the sysPass project pages for updates. For more recent vulnerability write-ups, browse the Webforta security blog.

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-129110: sysPass 3.0.1 through 3.2.11 contains an authentication bypass vulnerability that allows unauthenticated attackers to reinstall an already-installed instance…nvd.nist.gov ·
  • sysPass
  • CVE-2026-129110
  • authentication bypass
  • PHP
  • reinstall flaw