CVE-2026-25559
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenBullet2 through version 0.3.2 contains a path traversal vulnerability in the wordlist endpoint that allows authenticated attackers to perform arbitrary file read, write, and delete operations by supplying unsanitized absolute paths to the upload handler and wordlist functions. Attackers can chain the file write and delete primitives to achieve remote code execution by manipulating critical system files such as /etc/passwd, with full system impact since the application runs as root by default.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenBullet2 versions up to 0.3.2 contain a path traversal vulnerability in the wordlist endpoint that allows authenticated attackers to supply unsanitized absolute paths to perform arbitrary file read, write, and delete operations. Attackers can chain file write and delete primitives to achieve remote code execution by overwriting critical system files such as /etc/passwd, with full system impact since the application runs as root by default.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenBullet2 installation and versionLocate the OpenBullet2 application directory or executable, then check the version metadata (such as a version file, assembly info, or the executable's properties). Compare the found version to v0.3.2 or earlier.Affected if The installed version is v0.3.2 or any earlier version of OpenBullet2.
-
Confirm wordlist functionality is presentInspect the application's available endpoints or modules to verify the wordlist feature exists. Look for wordlist-related controllers, routes, or UI elements in the application.Affected if The wordlist feature is present in the installation.
-
Verify the wordlist endpoint is network-accessibleCheck the application's exposed network listeners or configuration files for HTTP/HTTPS bindings. Determine if the wordlist endpoint (typically under a /wordlist or similar path) is reachable over the network.Affected if The wordlist endpoint is accessible over the network without additional isolation.
-
Determine authentication configurationReview the application's authentication settings to confirm whether users must authenticate to access the wordlist endpoint. Check for session tokens, login requirements, or API key configurations.Affected if The wordlist endpoint permits access with valid user credentials, allowing an authenticated attacker to exploit the path traversal.
A user is affected if OpenBullet2 v0.3.2 or earlier is running with the wordlist feature enabled and accessible to authenticated users on the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation on the wordlist endpoint to reject absolute paths and sanitize path traversal sequences (..), and run the application with non-root privileges.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25559 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25559 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data