CVE-2026-3383
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 · uneditedA weakness has been identified in ChaiScript up to 6.1.0. This affects the function chaiscript::Boxed_Number::go of the file include/chaiscript/dispatchkit/boxed_number.hpp. Executing a manipulation can lead to divide by zero. The attack requires local access. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
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 · moderate confidenceA divide by zero vulnerability exists in ChaiScript's Boxed_Number::go function in the boxed_number.hpp file. Local attackers can exploit this by executing specific numeric operations that trigger the division by zero condition in the boxed number handling code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 6.1.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Verify ChaiScript installationSearch for ChaiScript libraries or binaries on the system. Common locations include /usr/lib/, /usr/local/lib/, or check package managers. Look for files named libchaiscript* or chaiscript binaries.Affected if ChaiScript is not found on the system, the vulnerability does not apply.
-
Determine installed ChaiScript versionCheck the version of the installed ChaiScript library or binary. If using a package manager, run 'dpkg -l libchaiscript*' or 'rpm -qa | grep chaiscript'. For compiled binaries, check any --version flag or inspect library version symbols.Affected if The installed version is 6.1.0 or lower.
-
Identify code execution pathsReview application code that invokes ChaiScript. Search for instances where ChaiScript::ChaiScript is instantiated and the eval() or run() methods are called with external or untrusted input.Affected if Untrusted or user-controlled input can be passed to ChaiScript evaluation functions.
-
Locate vulnerable source fileIf ChaiScript source code is present, verify the presence of boxed_number.hpp and inspect the Boxed_Number::go function for division operations without zero checks.Affected if The source file exists and contains the vulnerable division logic without proper zero checks.
-
Assess local access controlsReview system permissions and access controls around any ChaiScript execution endpoints. Determine if local unprivileged users can trigger ChaiScript code execution.Affected if Local attackers have the ability to invoke ChaiScript with crafted numeric operations.
You are affected if ChaiScript version 6.1.0 or lower is installed AND untrusted local users can execute ChaiScript numeric operations through your application.
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 dataUntil an official patch is released, restrict local access to ChaiScript executions and implement input validation to prevent the specific numeric operations that trigger the divide by zero. Monitor for vendor response and apply any future security updates promptly.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3383 — 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-3383 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