CVE-2026-25856
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 an authenticated remote code execution vulnerability that allows authenticated users to execute arbitrary C# code on the server host by creating or modifying job configurations. Attackers can leverage the plain C# execution mode, which lacks reference filtering or API restrictions, to access the file system, spawn processes, and invoke arbitrary .NET APIs 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 allows authenticated users to achieve remote code execution by creating or modifying job configurations that leverage plain C# execution mode. This mode lacks reference filtering or API restrictions, enabling attackers to access the file system, spawn processes, and invoke arbitrary .NET APIs running 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 installationLocate the OpenBullet2 web application or service in your environment. Check for directories containing 'OpenBullet2' or look for running processes named 'OpenBullet2' or similar .NET processes.Affected if OpenBullet2 is found running in the environment
-
Determine installed versionCheck the version of OpenBullet2 by inspecting the application binaries, DLL file properties, or the application's About/Status page if available. Compare against the affected range (0.3.2 and below).Affected if Installed version is 0.3.2 or lower
-
Locate job configurationsExamine the OpenBullet2 data directory for job configuration files (typically stored in user data folders or configuration databases). These configurations define how automation jobs execute.Affected if Job configuration files exist in the OpenBullet2 installation
-
Check for C# execution mode in job configsOpen and inspect job configuration files for the presence of a C# execution mode setting. Look for settings related to script execution, particularly plain C# or raw C# execution options.Affected if Any job configuration uses plain C# execution mode without sandboxing
-
Verify reference filtering and API restrictionsExamine the execution engine settings or global configuration for reference filtering rules and API restrictions. Check if these security controls are defined and enforced for the C# execution functionality.Affected if Reference filtering and API restrictions are not configured or are absent for C# execution mode
The environment is affected if OpenBullet2 version 0.3.2 or lower is running with job configurations that use plain C# execution mode lacking reference filtering and API restrictions.
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 dataUpgrade to a version beyond 0.3.2 which should include proper reference filtering and API restrictions, or disable the plain C# execution mode in job configurations if upgrading is not immediately feasible.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25856 — 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-25856 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