CVE
sysPass remote code execution in unauthenticated installer
Affects sysPass 3.0.1 through 3.2.11 on instances that are already installed, where the install/install handler can be reached and POSTed to. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
sysPass, from nuxsmin, is affected in versions from 3.0.1 through 3.2.11 (version numbers omitted per page rules). An attacker can reach the install handler remotely without logging in and reinstall an already-installed instance, which allows them to overwrite its configuration, point it at an attacker-controlled database, create an administrator account, and trigger planted serialized payloads to execute commands.
Read the original description
sysPass 3.0.1 through 3.2.11 contains an authentication bypass vulnerability that allows unauthenticated attackers to reinstall an already-installed instance by POSTing to the install/install handler, which never checks isInstalled(). Attackers can overwrite config.xml, point the application at an attacker-controlled database, create an administrator account, and plant serialized PublicLink gadget chains triggered via account/viewLink to execute commands.
Who should check
Teams running nuxsmin sysPass 3.0.1 through 3.2.11, including any already-installed instance reachable by unauthenticated requests to install/install.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
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-129110 (sysPass 3.0.1 through 3.2.11 Unauthenticated Reinstallation RCE via install/install), 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-129110 (entry last updated 2026-11-13):
Affected:
- nuxsmin sysPass: from 3.0.1, through 3.2.11
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- sysPass instance is already installed (reinstall of an existing instance) (source: https://www.vulncheck.com/advisories/syspass-3.0.1-through-3.2.11-unauthenticated-reinstallation-rce-via-install-install)
- sysPass versions 3.0.1 through 3.2.11 (source: https://www.vulncheck.com/advisories/syspass-3.0.1-through-3.2.11-unauthenticated-reinstallation-rce-via-install-install)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129110 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129110 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/OpusProjects/sysPass/pull/360
- https://github.com/nuxsmin/sysPass/issues/1954
- https://github.com/nuxsmin/sysPass/blob/3.2.11/app/modules/web/Controllers/InstallController.php#L80-L110
- https://github.com/nuxsmin/sysPass
- https://www.vulncheck.com/advisories/syspass-3.0.1-through-3.2.11-unauthenticated-reinstallation-rce-via-install-install
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-129110
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-129110"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- nuxsmin sysPass
From 3.0.1 · through 3.2.11
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129110
Is CVE-2026-129110 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?
The install/install handler can be used to reinstall an already-installed sysPass instance without logging in. A reinstall can overwrite config.xml and point the application at an attacker-controlled database. It can also create an administrator account and lead to command execution through planted serialized PublicLink data.Source: vulncheck.com
Which versions are affected by CVE-2026-129110?
sysPass: from 3.0.1 through 3.2.11.Source: cve.now feed data
Am I affected, and how do I check?
The reported range is sysPass 3.0.1 through 3.2.11, and the issue applies to an instance that is already installed. Compare the installed sysPass version with that range, and check whether the install handler is reachable on the instance. The checked facts do not give a specific version command or setting to use.Source: vulncheck.com
How do I fix CVE-2026-129110?
The checked facts do not name a fixed version or vendor patch identifiers, so no upgrade target can be stated from them. Check the vendor's sysPass advisory or release notes for a fix before relying on any version.Source: vulncheck.com