dbcve.org
ChaiscriptApplication

CVE-2026-3382

MEDIUM · 5.5 CVSS v3.1 Published 2026-03-01
Fix available
A fix is available. Upgrade to after 6.1.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
A security flaw has been discovered in ChaiScript up to 6.1.0. The impacted element is the function chaiscript::Boxed_Number::get_as of the file include/chaiscript/dispatchkit/boxed_number.hpp. Performing a manipulation results in memory corruption. The attack requires a local approach. The exploit has been released to the public and may 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 confidence

Memory corruption vulnerability in ChaiScript's Boxed_Number::get_as function in version 6.1.0 and earlier. The flaw allows local attackers to corrupt memory through the affected function in the boxed_number.hpp file, potentially leading to code execution or denial of service.

MitigationAvoid running untrusted ChaiScript code until an official patch is released. If running untrusted scripts is required, consider sandboxing the execution environment and monitoring for anomalous behavior.

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
ChaiscriptApplication
Affected:<= 6.1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ChaiScript installation
    Search for ChaiScript library files (.h, .hpp, .so, .dll, .dylib) or check build dependencies in your project
    Affected if ChaiScript files are found in the environment
  2. Determine ChaiScript version
    Check the version header file, library version metadata, or version string in the ChaiScript headers/libraries. Look for a version.h or version.hpp file, or check the library binary metadata
    Affected if The installed version is 6.1.0 or earlier, or the version cannot be determined (treat as vulnerable)
  3. Locate boxed_number.hpp in source
    Search for the file boxed_number.hpp in your ChaiScript source code or include directories
    Affected if The file exists and contains the Boxed_Number::get_as function implementation
  4. Verify usage of Boxed_Number::get_as
    Review application code or scripts that use ChaiScript to determine if Boxed_Number::get_as is called, particularly when processing numeric values from scripts
    Affected if The function is invoked to convert ChaiScript numeric values to C++ types
  5. Check if untrusted scripts are processed
    Audit the ChaiScript execution context to determine whether user-supplied or untrusted scripts are evaluated
    Affected if Untrusted ChaiScript code is executed in the environment

A user is affected if ChaiScript version 6.1.0 or earlier is present AND the Boxed_Number::get_as function processes untrusted script input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.1.0
Interim mitigation

Avoid running untrusted ChaiScript code until an official patch is released. If running untrusted scripts is required, consider sandboxing the execution environment and monitoring for anomalous behavior.

Recommended fix Low confidence

Check for ChaiScript version > 6.1.0 (such as 6.1.1 or later)

  1. 1. Check the official ChaiScript GitHub repository (github.com/ChaiScript/ChaiScript) for any releases newer than 6.1.0 that may contain security fixes
  2. 2. Review the project's security advisories or release notes for mention of CVE-2026-3382 or memory corruption fixes in boxed_number.hpp
  3. 3. If a fixed version (such as 6.1.1 or later) is available, upgrade to that version by updating your dependency configuration
  4. 4. If no fixed version exists, consider isolating ChaiScript execution in a sandboxed environment with limited privileges to mitigate local attack impact
  5. 5. Apply compiler hardening flags (-fstack-protector-all, -D_FORTIFY_SOURCE=2) as an additional mitigation layer
  6. 6. Monitor the ChaiScript GitHub repository for security updates or patches addressing this vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chaiscript Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3382 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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