CVE-2026-25855
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 remote code execution vulnerability that allows authenticated users to execute arbitrary commands by uploading script files (.bat.ps1.sh) through the FileProxySource proxy loading feature. Attackers can upload malicious script files as proxy sources, causing the server to execute the scripts and return output as proxy lines, resulting in arbitrary command execution on the host as the process user.
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 an RCE vulnerability in the FileProxySource feature where authenticated users can upload script files (.bat, .ps1, .sh) as proxy sources. The server executes these uploaded scripts and returns their output as proxy lines, allowing arbitrary command execution as the process user.
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 files or running process, then check the version number (typically in the application manifest, About page, or assembly metadata). Compare against the affected range (all versions through 0.3.2).Affected if OpenBullet2 version is 0.3.2 or earlier, or the exact version cannot be determined but the application is present.
-
Verify FileProxySource feature is configuredExamine the OpenBullet2 configuration files (typically stored in config or settings directories) for any FileProxySource entries, proxy source definitions, or references to proxy loading methods. Search for keywords: FileProxySource, FileProxy, proxy source type.Affected if The FileProxySource feature is enabled or configured in the application settings.
-
Confirm authentication is enabled for the vulnerable endpointReview the application authentication settings, user accounts, and access control configuration to determine whether users can authenticate to access the FileProxySource functionality.Affected if Authentication is enabled and untrusted or low-privilege users have access to the system.
-
Inspect proxy configurations for script file referencesSearch proxy configuration files, databases, or runtime settings for references to .bat, .ps1, or .sh file extensions in proxy source definitions.Affected if Any proxy configurations reference script files (.bat, .ps1, .sh) as proxy sources.
You are affected if OpenBullet2 version 0.3.2 or earlier is running with FileProxySource enabled and accessible to authenticated users, particularly if proxy configurations reference script files.
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 dataRestrict or disable the FileProxySource feature for untrusted users, implement strict allowlist validation for uploaded file types (reject .bat, .ps1, .sh), and ensure the application runs with minimal privileges to limit impact of potential compromise.
- Consultation3.0 h
- Implementation12.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 $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25855 — 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-25855 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